Try unplugging the FW power brick usb cable and plugging it back in again.
They appear here when I do that.
Yes, you are right, I am getting them too. Specifically, the error 256 one. I am also seeing a “spurious native interrupt” as the cable is connected:
[ 4030.360765] pcieport 0000:00:08.3: PME: Spurious native interrupt!
[ 4031.520528] ucsi_acpi USBC000:00: unknown error 256
[ 4031.520546] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
I’m seeing the same messages on my FW16, BIOS 3.03 (I think they may have started after the BIOS update), also running Arch. 2 USB-C cards in the back, 2 USB-A in the middle and MicroSD and audio cards in the front.
The messages normally occur three times:
Jun 02 10:29:40.283204 lotusdroid kernel: ucsi_acpi USBC000:00: unknown error 0
Jun 02 10:29:40.283459 lotusdroid kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
Jun 02 10:29:40.617206 lotusdroid kernel: ucsi_acpi USBC000:00: unknown error 256
Jun 02 10:29:40.617415 lotusdroid kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
Jun 02 10:29:40.842178 lotusdroid kernel: mt7921e 0000:01:00.0 wlp1s0: renamed from wlan0
Jun 02 10:29:40.926180 lotusdroid kernel: ucsi_acpi USBC000:00: unknown error 256
Jun 02 10:29:40.926456 lotusdroid kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
When all non-USB-C expansion cards are removed, with a charger plugged in during boot, it only happens once:
Jun 02 17:54:32.852988 lotusdroid kernel: ucsi_acpi USBC000:00: unknown error 256
Jun 02 17:54:32.853169 lotusdroid kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
This also happens whenever I plug in the charger, regardless of whether the other expansion cards are inserted.
Were you running Linux 6.9 (or any of its release candidates) before the BIOS upgrade?
I’m also getting this issue on my brand new FW16 running standard Arch. I updated to the newest BIOS and some other error messages went away but I’m still getting these. It also pops up again if I unplug/replug the power cable (in port 1). All in all the laptop seems to be functioning OK but it would be nice to figure out how to fix these errors.
Yes, although I’m not entirely certain the errors didn’t happen before the BIOS update.
I can add more context here for my situation. I was running a brand new minimal arch installation with linux kernal 6.9.3 and bios 0.3.2 and was definitely getting this error and this is still occurring for me on the same kernal version on bios 0.3.3. I’m poking around and doing my own research and will post back here if I find anything.
I’m also getting this on my FW16:
[ 2.824724] [ T172] ucsi_acpi USBC000:00: unknown error 0
[ 2.824751] [ T172] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
[ 3.495320] [ T172] ucsi_acpi USBC000:00: unknown error 256
[ 3.495357] [ T172] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
I was in batch 17 so I only just got it a few days ago and it’s been coming up with this message out of the box. I’m running OpenSUSE Tumbleweed on kernel 6.9.3 and bios 3.03. I tried reflashing the bios before I realised it was already on the latest and unsurprisingly it didn’t change anything. At first I wasn’t too worried about it, but I just had something really worrying happen:
[48614.361055] [T16283] BTRFS info (device dm-0): qgroup scan completed (inconsistency flag cleared)
[52218.691674] [T16886] BTRFS info (device dm-0): qgroup scan completed (inconsistency flag cleared)
[54833.024165] [T17820] ucsi_acpi USBC000:00: unknown error 256
[54833.024211] [T17820] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
[55826.270440] [ T5659] BTRFS info (device dm-0): qgroup scan completed (inconsistency flag cleared)
[56970.279447] [ T7969] ucsi_acpi USBC000:00: unknown error 256
[56970.279454] [ T7969] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
[56983.365308] [ T260] nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10
[56983.365322] [ T260] nvme nvme0: Does your device have a faulty power saving mode enabled?
[56983.365326] [ T260] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off" and report a bug
[56983.465295] [ T7969] nvme 0000:06:00.0: enabling device (0000 -> 0002)
[56983.465639] [ T7969] nvme nvme0: Disabling device after reset failure: -19
[56983.502005] [ T8812] BTRFS error (device dm-0): bdev /dev/mapper/system-root errs: wr 0, rd 0, flush 1, corrupt 0, gen 0
[56983.502037] [ T8812] BTRFS warning (device dm-0): chunk 13631488 missing 1 devices, max tolerance is 0 for writable mount
[56983.502042] [ T8812] BTRFS: error (device dm-0) in write_all_supers:4056: errno=-5 IO failure (errors while submitting device barriers.)
[56983.502051] [ T8812] BTRFS info (device dm-0 state E): forced readonly
[56983.502057] [ T8812] BTRFS error (device dm-0 state EA): Transaction aborted (error -5)
[56983.502077] [ T8812] BTRFS: error (device dm-0 state EA) in btrfs_sync_log:3164: errno=-5 IO failure
[56983.502542] [ T811] BTRFS warning (device dm-0 state EA): Skipping commit of aborted transaction.
[56983.502549] [ T811] BTRFS: error (device dm-0 state EA) in cleanup_transaction:2005: errno=-5 IO failure
Correlation isn’t causation and all that, but that’s a little too close for comfort. I’m wondering if this is actually causing real hardware issues.
Can’t say for sure, but I really doubt it. The ucsi_acpi messages seem to have been added in Linux 6.9 as a part of USB-C capabilities detection and surfacing through sysfs. Prior to that, if I understand it correctly, the related data points were not exposed through sysfs at all. I don’t see any way how failure to detect those capabilities would be related to either nvme, or the filesystem.
In any case, it appears that the USB-C cable capability detection added in 6.9 doesn’t work at all on FW AMD. Would be interesting to know the reason.
@Mario_Limonciello , is that something you are seeing as well?
1 Like
Yeah, that’s fair. I doubt it’s doing any harm to the hardware too, and I was a little imprecise. I meant to include things like driver issues in when I said “hardware issues”
To me the messages are issues with the EC or PD controller. It’s more likely PD controller, because I believe EC just passes the messages from OSPM back and forth in this case.
Can confirm that this issue is present with kernel 6.9.5 on Arch.
Jun 22 13:28:32 nyfb kernel: ucsi_acpi USBC000:00: unknown error 0
Jun 22 13:28:32 nyfb kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
I’m also still seeing this issue:
[ 340.257753] ucsi_acpi USBC000:00: unknown error 0
[ 340.257765] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
[ 341.274475] ucsi_acpi USBC000:00: unknown error 0
[ 341.274487] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
[ 342.277637] ucsi_acpi USBC000:00: unknown error 0
[ 342.277691] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
chris@victoria:~$ uname -r
6.10.2-arch1-1
chris@victoria:~$ sudo framework_tool --info
BIOS Information
Vendor: INSYDE Corp.
Version: 03.05
Release Date: 03/29/2024
System Information
Version: A7
Manufacturer: Framework
Product Name: Laptop 13 (AMD Ryzen 7040Series)
Wake-Up-Type: PowerSwitch
SKU Number: FRANDGCP07
Family: Laptop
I also have this message @Fedora40.
In addition to that, I observed the following problem:
USB-C Card in slot 1 has no display output. I attached a USB-docking (Anker) and this works except the video output. Then I tested around and it is not possible to get video out of this port, even with direct USB-C to HDMI cables… The USB-C card in port 3 works fine with dock and cable. Any suggestions?
Same issue here
- FW13 R7 7840U
- Debian testing/trixie
- kernel 6.10.6
not sure about boot time, but after reboot, all 4 usb ports (2-C, 2A) works fine
after some period of time, all stop working.
Sep 10 09:16:32 <hostname> kernel: ucsi_acpi USBC000:00: unknown error 0
Sep 10 09:16:32 <hostname> kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
appears when plugging in devices.
PD works fine, can identify 5A cable. but the error messages still pop.
When this happens, some devices still works,
- IS903 UFD, works, but dropped to USB2 high speed.
- USB3 GbE NIC, type-A, not work at all, no error message
- Logitech MX receiver, USB2 full-speed works,
- RTL9210B-CG M.2 enclosure, Type-A , works, dropped to USB2 HS
- RTL9210B-CG M.2 enclosure, Type-C , works, dropped to USB2 HS
My FWLT13 AMD outputs video via a USB-C to HDMI cable on port 1 fine with Windows. Maybe you need a more up-to-date Linux kernel?
FWIW, I have the same error on the latest Linux kernel AND with that kernel, I can’t get both of my external monitors to work at the same time, only one. They somehow get detected but no display signal is sent to 2nd one. Both monitors are connected via a Lenovo Thunderbolt 3 Dock.
Downgrading to the 6.6 LTS kernel fixes that issue.
Same. Laptop 13 (AMD Ryzen 7040Series) arrived recently. Running Tumbleweed. Wonder if it is causing my other (minor) issue:
“Battery at 99%, plugged in but still discharging” message pops up intermittently, but then says “Fully charged”.
> cat /etc/os-release
NAME="openSUSE Tumbleweed"
# VERSION="20240924"
ID="opensuse-tumbleweed"
ID_LIKE="opensuse suse"
VERSION_ID="20240924"
PRETTY_NAME="openSUSE Tumbleweed"
ANSI_COLOR="0;32"
# CPE 2.3 format, boo#1217921
CPE_NAME="cpe:2.3:o:opensuse:tumbleweed:20240924:*:*:*:*:*:*:*"
#CPE 2.2 format
#CPE_NAME="cpe:/o:opensuse:tumbleweed:20240924"
BUG_REPORT_URL="https://bugzilla.opensuse.org"
SUPPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org"
DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed"
LOGO="distributor-logo-Tumbleweed"
> sudo bin/framework_tool --info
Summary
Is Framework: true
Platform: Framework13Amd
BIOS Information
Vendor: INSYDE Corp.
Version: 03.05
Release Date: 03/29/2024
System Information
Version: Some(MassProduction) (A7)
Manufacturer: Framework
Product Name: Laptop 13 (AMD Ryzen 7040Series)
Wake-Up-Type: PowerSwitch
SKU Number: FRANDRCP07
Family: Laptop
BaseBoard Information
Version: Some(MassProduction) (A7)
Manufacturer: Framework
Product: FRANMDCP07
> sudo journalctl -g 'ucsi_acpi USB' -S 'Sep 26 10:00:00' | grep 'kernel'
Sep 26 10:13:06 localhost.localdomain kernel: ucsi_acpi USBC000:00: unknown error 256
Sep 26 10:13:06 localhost.localdomain kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
Sep 26 10:23:09 localhost kernel: ucsi_acpi USBC000:00: unknown error 0
Sep 26 10:23:09 localhost kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
Sep 26 10:23:10 localhost kernel: ucsi_acpi USBC000:00: unknown error 256
Sep 26 10:23:10 localhost kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
Sep 26 10:23:10 localhost kernel: ucsi_acpi USBC000:00: unknown error 256
Sep 26 10:23:10 localhost kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
Same. Laptop 13 (intel core ultra). Running either Rocky (with 6.11.6-1.el9.elrepo.x86_64) or Fedora. The issue is that it prevents me from using a device connected to it through USB-C directly. Bios is updated to 3.04 beta.
If I use a USB-C to USB-A dongle and a USB-A to USB-C to my device instead of USB-C to USB-C, it is working.
[Laptop FW-13 USB-C] ↔ [Device (USB-C)] ==> not working
[Laptop FW-13 USB-C] ↔ [USB-C → USB-A] ↔ [Device (USB-C)] ==> working
[ 2.188564] ucsi_acpi USBC000:00: unknown error 256
[ 2.188572] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
Is there any way to disable this behavior from the bios (I do not really need the PD directly, I would rather have a stable connexion).
Any updates on this issue, I get this problem also and it makes using external monitors via USBC to HDMI work irregularly. (Essentially when I see this the error the monitors are black but the os shows them as though they are there).
Linux fwbook 6.10.1-zen1 #1-NixOS ZEN SMP PREEMPT_DYNAMIC Tue Jan 1 00:00:00 UTC 1980 x86_64 GNU/Linux
BIOS Information
Vendor: INSYDE Corp.
Version: 03.05
Release Date: 03/29/2024
System Information
Version: A5
Manufacturer: Framework
Product Name: Laptop 13 (AMD Ryzen 7040Series)
Wake-Up-Type: PowerSwitch
SKU Number: FRANMDCP05
Family: Laptop