All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	Nathan Rebello <nathan.c.rebello@gmail.com>,
	Heikki Krogerus <heikki.krogerus@linux.intel.com>
Subject: Re: Spurious errors "ucsi_acpi USBC000:00: bogus connector number in CCI: 1" on 7.0-rc7
Date: Tue, 7 Apr 2026 07:58:08 +0200	[thread overview]
Message-ID: <2026040734-headfirst-tingly-e6ea@gregkh> (raw)
In-Reply-To: <875x63gwid.wl-tiwai@suse.de>

On Tue, Apr 07, 2026 at 07:38:50AM +0200, Takashi Iwai wrote:
> Hi,
> 
> since 7.0-rc7, I'm getting a few errors
>   ucsi_acpi USBC000:00: bogus connector number in CCI: 1
> at boot of Thinkpad T14s Gen 6 AMD with a dock.
> 
> Obviously this came from the commit d2d8c17ac01a ("usb: typec: ucsi:
> validate connector number in ucsi_notify_common()"), and reverting it
> made it gone away.  I didn't notice anything practically broken either
> before or after the revert, though -- the USB devices connected on the
> dock keep working, at least.
> 
> Is this a firmware bug, or some missing piece in the code?
> Judging from the message, it means that ucsi->cap.num_connectors is 0,
> I suppose.

Ugh, what's the odds this is an off-by-one error in the firmware? :)

Nathan and Heikki, any ideas?

thanks,

greg k-h

  reply	other threads:[~2026-04-07  5:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-07  5:38 Spurious errors "ucsi_acpi USBC000:00: bogus connector number in CCI: 1" on 7.0-rc7 Takashi Iwai
2026-04-07  5:58 ` Greg Kroah-Hartman [this message]
2026-04-07  6:21   ` Nathan Rebello

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=2026040734-headfirst-tingly-e6ea@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=nathan.c.rebello@gmail.com \
    --cc=tiwai@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.