From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 219590] Linux 6.13 ucsi driver error: drivers/usb/typec/ucsi/ucsi.c:1374 ucsi_reset_ppm
Date: Tue, 18 Feb 2025 18:44:05 +0000 [thread overview]
Message-ID: <bug-219590-208809-YfBA5YhZNc@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219590-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219590
RockT (tr.ml@gmx.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tr.ml@gmx.de
--- Comment #15 from RockT (tr.ml@gmx.de) ---
I see it in 6.14rc3:
[ 11.560861] WARNING: CPU: 4 PID: 81 at drivers/usb/typec/ucsi/ucsi.c:1377
ucsi_reset_ppm+0x1ad/0x1c0 [typec_ucsi]
[ 11.560897] Modules linked in: dm_crypt raid10 raid456 async_raid6_recov
async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 linear
dm_mirror dm_region_hash dm_log hid_logitech_hidpp hid_logitech_dj hid_generic
usbhid hid polyval_clmulni rtsx_pci_sdmmc polyval_generic ghash_clmulni_intel
nvme thinkpad_acpi ucsi_acpi sha256_ssse3 sha1_ssse3 e1000e psmouse nvram
nvme_core rtsx_pci intel_lpss_pci typec_ucsi nvme_auth intel_lpss snd typec
idma64 soundcore sparse_keymap video platform_profile wmi pinctrl_cannonlake
aesni_intel crypto_simd cryptd
[ 11.561052] CPU: 4 UID: 0 PID: 81 Comm: kworker/4:1 Not tainted
6.14.0-061400rc3-generic #202502181422
[ 11.561064] Hardware name: LENOVO 20Q5CTO1WW/20Q5CTO1WW, BIOS R0ZET58W (1.36
) 02/22/2024
[ 11.561072] Workqueue: events_long ucsi_init_work [typec_ucsi]
[ 11.561096] RIP: 0010:ucsi_reset_ppm+0x1ad/0x1c0 [typec_ucsi]
[ 11.561115] Code: ff 8b 55 bc 81 e2 00 00 00 08 0f 85 33 ff ff ff 4c 89 75
c8 48 8b 05 52 9d 10 dc 49 39 c5 79 94 b8 92 ff ff ff e9 19 ff ff ff <0f> 0b e9
57 ff ff ff e8 e7 28 01 db 0f 1f 80 00 00 00 00 90 90 90
[ 11.561123] RSP: 0018:ffffad1600363d70 EFLAGS: 00010206
[ 11.561134] RAX: 0000000008000000 RBX: ffff9e340ec78000 RCX:
0000000000000000
[ 11.561141] RDX: 00000000fffb97aa RSI: 0000000000000000 RDI:
0000000000000000
[ 11.561146] RBP: ffffad1600363dc0 R08: 0000000000000000 R09:
0000000000000000
[ 11.561152] R10: 0000000000000000 R11: 0000000000000000 R12:
ffffad1600363d7c
[ 11.561157] R13: 00000000fffb9797 R14: ffff9e340ec78020 R15:
ffff9e340ec780c0
[ 11.561164] FS: 0000000000000000(0000) GS:ffff9e3b5e600000(0000)
knlGS:0000000000000000
[ 11.561172] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 11.561178] CR2: 00005bd21fb4c028 CR3: 0000000170240004 CR4:
00000000003706f0
[ 11.561186] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
[ 11.561190] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7:
0000000000000400
[ 11.561196] Call Trace:
[ 11.561202] <TASK>
[ 11.561209] ? show_trace_log_lvl+0x1be/0x310
[ 11.561224] ? show_trace_log_lvl+0x1be/0x310
[ 11.561237] ? ucsi_init+0x2bc/0x310 [typec_ucsi]
[ 11.561257] ? show_regs.part.0+0x22/0x30
[ 11.561267] ? show_regs.cold+0x8/0x10
[ 11.561277] ? ucsi_reset_ppm+0x1ad/0x1c0 [typec_ucsi]
[ 11.561293] ? __warn.cold+0xac/0x10c
[ 11.561304] ? ucsi_reset_ppm+0x1ad/0x1c0 [typec_ucsi]
[ 11.561320] ? report_bug+0x114/0x160
[ 11.561332] ? handle_bug+0x6e/0xb0
[ 11.561343] ? exc_invalid_op+0x18/0x80
[ 11.561354] ? asm_exc_invalid_op+0x1b/0x20
[ 11.561369] ? ucsi_reset_ppm+0x1ad/0x1c0 [typec_ucsi]
[ 11.561386] ? ucsi_send_command_common+0xa4/0x120 [typec_ucsi]
[ 11.561404] ucsi_init+0x2bc/0x310 [typec_ucsi]
[ 11.561422] ucsi_init_work+0x18/0x90 [typec_ucsi]
[ 11.561439] process_one_work+0x174/0x350
[ 11.561456] worker_thread+0x34a/0x480
[ 11.561464] ? _raw_spin_lock_irqsave+0xe/0x20
[ 11.561478] ? __pfx_worker_thread+0x10/0x10
[ 11.561486] kthread+0xf9/0x230
[ 11.561497] ? __pfx_kthread+0x10/0x10
[ 11.561508] ret_from_fork+0x44/0x70
[ 11.561518] ? __pfx_kthread+0x10/0x10
[ 11.561527] ret_from_fork_asm+0x1a/0x30
[ 11.561545] </TASK>
[ 11.561549] ---[ end trace 0000000000000000 ]---
[ 11.601285] ucsi_acpi USBC000:00: error -ETIMEDOUT: PPM init failed
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2025-02-18 18:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 13:23 [Bug 219590] New: Linux 6.13 ucsi driver error bugzilla-daemon
2024-12-30 21:54 ` [Bug 219590] " bugzilla-daemon
2025-01-01 11:33 ` bugzilla-daemon
2025-01-13 10:26 ` [Bug 219590] Linux 6.13 ucsi driver error: drivers/usb/typec/ucsi/ucsi.c:1374 ucsi_reset_ppm bugzilla-daemon
2025-01-13 12:39 ` bugzilla-daemon
2025-01-13 18:54 ` bugzilla-daemon
2025-01-23 10:43 ` bugzilla-daemon
2025-02-01 21:15 ` bugzilla-daemon
2025-02-01 21:16 ` bugzilla-daemon
2025-02-01 21:20 ` bugzilla-daemon
2025-02-03 17:24 ` bugzilla-daemon
2025-02-03 17:29 ` bugzilla-daemon
2025-02-03 18:28 ` bugzilla-daemon
2025-02-06 13:22 ` bugzilla-daemon
2025-02-06 13:53 ` bugzilla-daemon
2025-02-18 18:44 ` bugzilla-daemon [this message]
2025-03-05 10:28 ` bugzilla-daemon
2025-03-16 19:50 ` bugzilla-daemon
2025-03-17 17:57 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-219590-208809-YfBA5YhZNc@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).