Re: GET_CABLE_PROPERTY issue

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Nicolas,

Let's have the discussion on the mailing list.

On Fri, Nov 08, 2024 at 08:35:06AM +0000, nicolas.oury@xxxxxxxxx wrote:
> Hello,
> 
> I am sorry to disturb you but I am not sure what is the proper way to
> report this.
> Please let me know what would be a better channel to report this issue.
> 
> I am on a Framework 16 AMD and have this message on boot:
> 
> [    1.705612] ucsi_acpi USBC000:00: unknown error 0
> [    1.707485] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
> [    2.869536] ucsi_acpi USBC000:00: unknown error 256
> [    2.870668] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
> 
> It seems to be fairly frequent:
> https://community.frame.work/t/usb-c-error-on-boot/52012
> 
> I digged a bit, and it seems to have started with :
> https://lore.kernel.org/all/20240305025804.1290919-3-jthies@xxxxxxxxxx/
> 
> Looking at the USCI specification, it seems that 0 and 256 are telling
> that this does not support the GET_CABLE_PROPERTY. This seems weird as
> your patch asks whether it supports this call before doing it.

+James

> The framework have many converters from usb C to usb A for modularity
> and I could try removing some of them to check which trigger this, it
> you find it helpful.
> 
> I am also very happy to help in any way.

You need to report this to AMD. The driver has to be able to rely on
what the interface is telling it. In this case the interface is
claiming that the Cable Details feature is supported, even though it
clearly is not.

Br,

-- 
heikki




[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux