Battery at 90%, connected to charger, no change - both fwupdmgr and USB stick updates fail still 
Tried again via fwupdmgr, got EFI Error Code 03 this time. No hits on Google as to what this means… anyone else know ?
@Kieran_Levin @Matt_Hartley I was able to reproduce the issue with two chargers and one 65W USB PD Power Bank.
Steps to reproduce:
- Shut down Linux.
- Plug charger into left rear USB C expansion port first.
- Plug charger into wall socket or turn on Power Bank.
- Charging indicator is showing full charge and Framework isn’t charging. Although battery isn’t fully charged.
If I reverse steps 2 and 3 or turn it on, all those chargers successfully charge my device.
One thing I noticed is the red charging light flashes a few times before settling on red. Is it possible USB PD is failing to settle in time?!?
Is there a way to downgrade?
I am having issues where bluetooth disconnects randomly (Windows/Linux), windows not waking up from sleep and its laggy in the UEFI menu. This is not a great experience.
Everything was working fine before in windows and linux with the 6.6 rc kernel.
After some investigation I noticed this in my kernel messaging:
[ 102.200504] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
[ 104.193968] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
[ 104.194129] usb usb1-port1: attempt power cycle
[ 106.466418] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
[ 108.253505] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
[ 108.253643] usb usb1-port1: unable to enumerate USB device
[ 124.267427] xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
[ 129.221084] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
[ 131.421719] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
[ 131.421861] usb usb1-port1: attempt power cycle
[ 133.488321] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
[ 135.484322] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
[ 135.484393] usb usb1-port1: unable to enumerate USB device
[ 137.753685] xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
[ 142.720766] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
[ 144.930714] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
[ 144.930780] usb usb1-port1: attempt power cycle
[ 147.004217] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
[ 148.801369] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
[ 148.801481] usb usb1-port1: unable to enumerate USB device
[ 149.997059] xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
[ 154.947987] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
[ 157.147871] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
[ 157.148007] usb usb1-port1: attempt power cycle
On this hunch, I tried a different USB-C PD charger, even though both say they do 65W at up to 20V@3.25A. Red light went solid much faster with this one.
fwupdmgr worked first time (battery at 72% and connected to charger) ! Hurrah !
Working charger : https://www.amazon.co.uk/dp/B08CDDSVN4?ref=ppx_yo2ov_dt_b_product_details&th=1
Be aware that as pictured it is a UK plug, if you are not in the UK, and I don’t see it as having swapable pins like the white one might have.
That’s a risk if you buy from a co.uk. You can’t change the pins, no. Note that’s not my picture, it’s the shops.
With the edge at half a metre the plug style is secondary IMHO.
Anyway - I will be testing with what I already have (Zendure, ChargeASAP, Spigen), including powerbanks.
The experience has been mostly stable for me on F39 beta.
I did see the artifacts on screen after about spending two days going in and out of suspend several times throughout the day.
I also randomly got an issue where everything ran very slow, such as moving a cursor took 5 seconds to register. A reboot resolved that but wasn’t able to find a log in the broken state.
I did notice some bios bugs in dmesg, but given that is very accessible it might be known already. I cannot attach it, so here is what I think to be the relevant information from it:
[ 0.003991] ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20230331/tbfadt-615)
Context below:09ooooooooooooooooooooooooooooooooooo56
[ 0.000000] Linux version 6.5.6-300.fc39.x86_64 (mockbuild@fe458d2eae0b4ff0bb0a00a41dbf9744) (gcc (GCC) 13.2.1 20230918 (Red Hat 13.2.1-3), GNU ld version 2.40-13.fc39) #1 SMP PREEMPT_DYNAMIC Fri Oct 6 19:57:21 UTC 2023
[ 0.000000] Command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.5.6-300.fc39.x86_64 root=UUID=74d4678b-4761-404b-ad83-205fc4605f6a ro rootflags=subvol=root rd.luks.uuid=luks-a85ccd38-a709-483c-bd47-c5af0e4facdc rhgb quiet
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009f000-0x00000000000bffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000000009afffff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000009b00000-0x0000000009dfffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000009e00000-0x0000000009efffff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000009f00000-0x0000000009f3bfff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x0000000009f3c000-0x000000004235ffff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000042360000-0x000000004455ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000044560000-0x0000000044568fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000044569000-0x000000004456cfff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000004456d000-0x000000004456efff] usable
[ 0.000000] BIOS-e820: [mem 0x000000004456f000-0x000000004456ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000044570000-0x000000005077efff] usable
[ 0.000000] BIOS-e820: [mem 0x000000005077f000-0x0000000052f7efff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000052f7f000-0x000000005af7efff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x000000005af7f000-0x000000005affefff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x000000005afff000-0x000000005affffff] usable
[ 0.000000] BIOS-e820: [mem 0x000000005b000000-0x000000005bffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000005d790000-0x000000005d7effff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000005d7f5000-0x000000005fffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000c0300000-0x00000000c03fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed80000-0x00000000fed80fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087e2fffff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000880000000-0x00000008c01fffff] reserved
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] e820: update [mem 0x4049b018-0x4049f257] usable ==> usable
[ 0.000000] e820: update [mem 0x4049b018-0x4049f257] usable ==> usable
[ 0.000000] extended physical RAM map:
[ 0.000000] reserve setup_data: [mem 0x0000000000000000-0x000000000009efff] usable
[ 0.000000] reserve setup_data: [mem 0x000000000009f000-0x00000000000bffff] reserved
[ 0.000000] reserve setup_data: [mem 0x0000000000100000-0x0000000009afffff] usable
[ 0.000000] reserve setup_data: [mem 0x0000000009b00000-0x0000000009dfffff] reserved
[ 0.000000] reserve setup_data: [mem 0x0000000009e00000-0x0000000009efffff] usable
[ 0.000000] reserve setup_data: [mem 0x0000000009f00000-0x0000000009f3bfff] ACPI NVS
[ 0.000000] reserve setup_data: [mem 0x0000000009f3c000-0x000000004049b017] usable
[ 0.000000] reserve setup_data: [mem 0x000000004049b018-0x000000004049f257] usable
[ 0.000000] reserve setup_data: [mem 0x000000004049f258-0x000000004235ffff] usable
[ 0.000000] reserve setup_data: [mem 0x0000000042360000-0x000000004455ffff] reserved
[ 0.000000] reserve setup_data: [mem 0x0000000044560000-0x0000000044568fff] usable
[ 0.000000] reserve setup_data: [mem 0x0000000044569000-0x000000004456cfff] reserved
[ 0.000000] reserve setup_data: [mem 0x000000004456d000-0x000000004456efff] usable
[ 0.000000] reserve setup_data: [mem 0x000000004456f000-0x000000004456ffff] reserved
[ 0.000000] reserve setup_data: [mem 0x0000000044570000-0x000000005077efff] usable
[ 0.000000] reserve setup_data: [mem 0x000000005077f000-0x0000000052f7efff] reserved
[ 0.000000] reserve setup_data: [mem 0x0000000052f7f000-0x000000005af7efff] ACPI NVS
[ 0.000000] reserve setup_data: [mem 0x000000005af7f000-0x000000005affefff] ACPI data
[ 0.000000] reserve setup_data: [mem 0x000000005afff000-0x000000005affffff] usable
[ 0.000000] reserve setup_data: [mem 0x000000005b000000-0x000000005bffffff] reserved
[ 0.000000] reserve setup_data: [mem 0x000000005d790000-0x000000005d7effff] reserved
[ 0.000000] reserve setup_data: [mem 0x000000005d7f5000-0x000000005fffffff] reserved
[ 0.000000] reserve setup_data: [mem 0x00000000c0300000-0x00000000c03fffff] reserved
[ 0.000000] reserve setup_data: [mem 0x00000000fed80000-0x00000000fed80fff] reserved
[ 0.000000] reserve setup_data: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[ 0.000000] reserve setup_data: [mem 0x0000000100000000-0x000000087e2fffff] usable
[ 0.000000] reserve setup_data: [mem 0x0000000880000000-0x00000008c01fffff] reserved
[ 0.000000] efi: EFI v2.8 by INSYDE Corp.
[ 0.000000] efi: ACPI=0x5affe000 ACPI 2.0=0x5affe014 TPMFinalLog=0x5af3f000 SMBIOS=0x51677000 SMBIOS 3.0=0x51674000 MEMATTR=0x4b80f018 ESRT=0x4d16b898 MOKvar=0x5187c000 RNG=0x5af9b018 TPMEventLog=0x4048a018
[ 0.000000] random: crng init done
[ 0.000000] efi: Remove mem70: MMIO range=[0xc0300000-0xc03fffff] (1MB) from e820 map
[ 0.000000] e820: remove [mem 0xc0300000-0xc03fffff] reserved
[ 0.000000] efi: Not removing mem71: MMIO range=[0xfed80000-0xfed80fff] (4KB) from e820 map
[ 0.000000] efi: Remove mem72: MMIO range=[0xff000000-0xffffffff] (16MB) from e820 map
[ 0.000000] e820: remove [mem 0xff000000-0xffffffff] reserved
[ 0.000000] efi: Remove mem74: MMIO range=[0x8a0000000-0x8c01fffff] (514MB) from e820 map
[ 0.000000] e820: remove [mem 0x8a0000000-0x8c01fffff] reserved
[ 0.000000] secureboot: Secure boot enabled
[ 0.000000] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7
[ 0.000000] SMBIOS 3.5.0 present.
[ 0.000000] DMI: Framework Laptop 13 (AMD Ryzen 7040Series)/FRANMDCP07, BIOS 03.03 10/17/2023
[ 0.000000] tsc: Fast TSC calibration using PIT
[ 0.000000] tsc: Detected 3293.808 MHz processor
[ 0.000124] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[ 0.000125] e820: remove [mem 0x000a0000-0x000fffff] usable
[ 0.000131] last_pfn = 0x87e300 max_arch_pfn = 0x400000000
[ 0.000137] MTRR map: 7 entries (3 fixed + 4 variable; max 20), built from 9 variable MTRRs
[ 0.000138] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT
[ 0.000630] last_pfn = 0x5b000 max_arch_pfn = 0x400000000
[ 0.003353] esrt: Reserving ESRT space from 0x000000004d16b898 to 0x000000004d16b8d0.
[ 0.003358] e820: update [mem 0x4d16b000-0x4d16bfff] usable ==> reserved
[ 0.003374] Using GB pages for direct mapping
[ 0.003975] secureboot: Secure boot enabled
[ 0.003976] RAMDISK: [mem 0x3c4ee000-0x3f941fff]
[ 0.003979] ACPI: Early table checksum verification disabled
[ 0.003982] ACPI: RSDP 0x000000005AFFE014 000024 (v02 INSYDE)
[ 0.003984] ACPI: XSDT 0x000000005AF9E228 00017C (v01 INSYDE EDK2 00000002 01000013)
[ 0.003988] ACPI: FACP 0x000000005AFEE000 00010C (v05 INSYDE EDK2 00000002 ACPI 00040000)
[ 0.003991] ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20230331/tbfadt-615)
[ 0.003994] ACPI: DSDT 0x000000005AFDE000 0093A6 (v02 INSYDE EDK2 00000002 ACPI 00040000)
[ 0.003995] ACPI: FACS 0x000000005AEB4000 000040
[ 0.003997] ACPI: UEFI 0x000000005AF67000 0001CF (v01 INSYDE EDK2 00000001 ACPI 00040000)
[ 0.003998] ACPI: SSDT 0x000000005AFF4000 008416 (v02 INSYDE EDK2 00000002 ACPI 00040000)
[ 0.003999] ACPI: SSDT 0x000000005AFF3000 00033E (v01 INSYDE EDK2 00001000 ACPI 00040000)
[ 0.004001] ACPI: SSDT 0x000000005AFF1000 000ABD (v02 INSYDE EDK2 00001000 ACPI 00040000)
[ 0.004002] ACPI: ASF! 0x000000005AFF0000 0000A5 (v32 INSYDE EDK2 00000002 ACPI 00040000)
[ 0.004004] ACPI: BOOT 0x000000005AFEF000 000028 (v01 INSYDE EDK2 00000002 ACPI 00040000)
[ 0.004005] ACPI: HPET 0x000000005AFED000 000038 (v01 INSYDE EDK2 00000002 ACPI 00040000)
[ 0.004006] ACPI: APIC 0x000000005AFEC000 000138 (v03 INSYDE EDK2 00000002 ACPI 00040000)
[ 0.004008] ACPI: MCFG 0x000000005AFEB000 00003C (v01 INSYDE EDK2 00000002 ACPI 00040000)
[ 0.004009] ACPI: SLIC 0x000000005AFEA000 000176 (v01 INSYDE EDK2 00000002 ACPI 00040000)
[ 0.004011] ACPI: VFCT 0x000000005AFD9000 004284 (v01 INSYDE EDK2 00000001 ACPI 00040000)
[ 0.004012] ACPI: SSDT 0x000000005AFD8000 0000F8 (v02 INSYDE EDK2 00001000 ACPI 00040000)
[ 0.004013] ACPI: SSDT 0x000000005AFD2000 00547E (v02 INSYDE EDK2 00000001 ACPI 00040000)
[ 0.004015] ACPI: CRAT 0x000000005AFD1000 000F10 (v01 INSYDE EDK2 00000001 ACPI 00040000)
[ 0.004016] ACPI: CDIT 0x000000005AFD0000 000029 (v01 INSYDE EDK2 00000001 ACPI 00040000)
[ 0.004017] ACPI: SSDT 0x000000005AFCF000 000F8D (v02 INSYDE EDK2 00000001 ACPI 00040000)
[ 0.004019] ACPI: SSDT 0x000000005AFCE000 000EC1 (v02 INSYDE EDK2 00000001 ACPI 00040000)
[ 0.004020] ACPI: SSDT 0x000000005AFFD000 000931 (v02 INSYDE EDK2 00000001 ACPI 00040000)
[ 0.004021] ACPI: SSDT 0x000000005AFCB000 0013EC (v02 INSYDE EDK2 00000001 ACPI 00040000)
[ 0.004023] ACPI: SSDT 0x000000005AFCA000 00077A (v02 INSYDE EDK2 00000001 ACPI 00040000)
[ 0.004024] ACPI: SSDT 0x000000005AFC9000 000737 (v02 INSYDE EDK2 00000001 ACPI 00040000)
[ 0.004025] ACPI: SSDT 0x000000005AFC7000 0015C8 (v02 INSYDE EDK2 00000001 ACPI 00040000)
[ 0.004027] ACPI: SSDT 0x000000005AFC4000 002A8F (v02 INSYDE EDK2 00000001 ACPI 00040000)
[ 0.004028] ACPI: SSDT 0x000000005AFBA000 009821 (v02 INSYDE EDK2 00000001 ACPI 00040000)
[ 0.004029] ACPI: FPDT 0x000000005AFB9000 000044 (v01 INSYDE EDK2 00000002 ACPI 00040000)
[ 0.004031] ACPI: WSMT 0x000000005AFB7000 000028 (v01 INSYDE EDK2 00000001 ACPI 00040000)
[ 0.004032] ACPI: TPM2 0x000000005AFE9000 000050 (v05 INSYDE EDK2 20505348 ACPI 00040000)
[ 0.004034] ACPI: MHSP 0x000000005AFE8000 0000C8 (v04 INSYDE EDK2 20505348 ACPI 00040000)
[ 0.004035] ACPI: SSDT 0x000000005AFB6000 0000E5 (v02 INSYDE EDK2 00000004 ACPI 00040000)
[ 0.004036] ACPI: IVRS 0x000000005AFB5000 0001A4 (v02 INSYDE EDK2 00000001 ACPI 00040000)
[ 0.004038] ACPI: SSDT 0x000000005AFB4000 000747 (v02 INSYDE EDK2 00000001 ACPI 00040000)
[ 0.004039] ACPI: SSDT 0x000000005AFB3000 000C88 (v02 INSYDE EDK2 00000001 ACPI 00040000)
[ 0.004040] ACPI: SSDT 0x000000005AFB2000 000057 (v02 INSYDE EDK2 00000001 ACPI 00040000)
[ 0.004042] ACPI: SSDT 0x000000005AFB0000 00170B (v02 INSYDE EDK2 00000001 ACPI 00040000)
[ 0.004043] ACPI: SSDT 0x000000005AFAF000 000FF7 (v02 INSYDE EDK2 00000001 ACPI 00040000)
[ 0.004044] ACPI: SSDT 0x000000005AFA5000 0097E3 (v02 INSYDE EDK2 00000001 ACPI 00040000)
[ 0.004046] ACPI: SSDT 0x000000005AFA0000 004FEB (v02 INSYDE EDK2 00000001 ACPI 00040000)
[ 0.004047] ACPI: SSDT 0x000000005AF9F000 000C7F (v02 INSYDE EDK2 00000001 ACPI 00040000)
[ 0.004048] ACPI: SSDT 0x000000005AFCD000 000956 (v02 INSYDE EDK2 00000001 ACPI 00040000)
[ 0.004050] ACPI: SSDT 0x000000005AF9D000 00008D (v02 INSYDE EDK2 00000001 ACPI 00040000)
[ 0.004051] ACPI: SSDT 0x000000005AF9C000 000EAD (v02 INSYDE EDK2 00000001 ACPI 00040000)
[ 0.004052] ACPI: BGRT 0x000000005AFB8000 000038 (v01 INSYDE EDK2 00000002 ACPI 00040000)
[ 0.004054] ACPI: Reserving FACP table memory at [mem 0x5afee000-0x5afee10b]
1 Like
I’m a little disappointed in Framework for still not mentioning this in their beta posts, but no, running this upgrade is a risk because there is no way to go back, which is why it is a beta, and not a release. By choosing to install the new BIOS you risk any issues that could occur.
That said, are you seeing these issues in both Windows and Linux? It might be worthwhile to try a live-usb of fedora or ubuntu to see if there is a chance that something got changed in your install that are causing these issues. Hopefully Framework staff are also able to see your post this week and help you out more.
I’m on windows, and actually see a performance bump with 3.03 weirdly enough. One thing I do notice both with framework provided drivers and AMD drivers is a graphical bug in OneNote, where the content will go completely white and only goes back if you either scroll or select the thing under the white box. Also on some fullscreen games it’ll freak out and blank the screen, with a ctrl alt delete bringing it back, but then it’ll go back to freaking out.
Alright, this one is probably easy to fix, low priority, but driving me crazy.
Closing the lid triggers a wake-up. If you put the computer into suspend and close it on something thin so you can see past the screen gasket… the screen turns on.
The lid close event/signal is waking the computer. I think that’s incorrect behavior. I’ve disabled all ACPI wake-up devices but it’s still doing this, it makes sense that this is probably being handled by the BIOS. No DE/WM, at a plain vt, it’s still doing this behavior.
I think two changes would help here and honestly all machines where Framework is customizing BIOSes:
- Only wake-up on lid open and ignore lid close while suspended (if it’s possible with the BIOS)
- Ability* to disable the lid completely as a wake-up source via BIOS
Please 
> enzi@ultraportable: ~
$ dmesg | grep -i -C 1 -e fail -e error -e bug -e issue -e crash -e oops
[ 0.003281] ACPI: FACP 0x000000005AFEF000 00010C (v05 INSYDE EDK2 00000002 ACPI 00040000)
[ 0.003284] ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20230331/tbfadt-615)
[ 0.003286] ACPI: DSDT 0x000000005AFDF000 0093A6 (v02 INSYDE EDK2 00000002 ACPI 00040000)
--
[ 0.361843] PCI: not using MMCONFIG
[ 0.361845] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 0.361847] PCI: Ignoring E820 reservations for host bridge windows
--
[ 0.441676] usbcore: registered new interface driver usbtv
[ 0.441965] fail to initialize ptp_kvm
[ 0.442063] device-mapper: ioctl: 4.48.0-ioctl (2023-03-01) initialised: dm-devel@redhat.com
--
[ 0.479083] Btrfs loaded, zoned=no, fsverity=no
[ 0.479425] pstore: Using crash dump compression: deflate
[ 0.479912] PM: Magic number: 11:63:177
--
[ 0.483010] Loading firmware: regulatory.db
[ 0.483276] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 0.483552] cfg80211: failed to load regulatory.db
[ 0.484032] clk: Disabling unused clocks
--
[ 1.471042] clocksource: Switched to clocksource tsc
[ 8.255081] ucsi_acpi USBC000:00: ucsi_handle_connector_change: ACK failed (-110)
[ 13.375080] ucsi_acpi USBC000:00: ucsi_handle_connector_change: ACK failed (-110)
[ 18.494506] ucsi_acpi USBC000:00: ucsi_handle_connector_change: ACK failed (-110)
[ 19.245170] exFAT-fs (dm-0): invalid boot record signature
[ 19.245174] exFAT-fs (dm-0): failed to read boot sector
[ 19.245175] exFAT-fs (dm-0): failed to recognize exfat type
[ 19.249545] BTRFS: device fsid 9e95fabc-0b33-4819-b2cd-c7598f5e1c9e devid 1 transid 29021 /dev/mapper/root scanned by exe (2196)
--
[ 54.276254] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
[ 54.276262] printk: Suspending console(s) (use no_console_suspend to debug)
[ 54.454865] ACPI: EC: interrupt blocked
--
[ 66.331833] nvme nvme0: 16/0/0 default/read/poll queues
[ 66.461744] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
[ 66.461808] [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
[ 66.463889] [drm] PCIE GART of 512M enabled (table at 0x000000801FD00000).
--
[ 70.187918] wlp1s0: Limiting TX power to 0 (-128 - 0) dBm as advertised by 86:c0:8f:b9:12:51
[ 71.654785] ucsi_acpi USBC000:00: ucsi_handle_connector_change: ACK failed (-110)
[ 71.769606] ------------[ cut here ]------------
--
[ 71.769762] ? rcu_note_context_switch+0x49c/0x4e0
[ 71.769766] ? report_bug+0x189/0x1c0
[ 71.769773] ? handle_bug+0x36/0x70
[ 71.769778] ? exc_invalid_op+0x13/0x60
--
[ 71.770014] ---[ end trace 0000000000000000 ]---
[ 77.286751] ucsi_acpi USBC000:00: ucsi_handle_connector_change: ACK failed (-110)
[ 93.487931] elogind-daemon[3675]: Power key pressed.
--
[ 94.077480] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
[ 94.077490] printk: Suspending console(s) (use no_console_suspend to debug)
[ 94.262707] ACPI: EC: interrupt blocked
--
[ 98.784022] nvme nvme0: 16/0/0 default/read/poll queues
[ 98.923463] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
[ 98.923548] [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
[ 98.925525] [drm] PCIE GART of 512M enabled (table at 0x000000801FD00000).
--
[ 102.182375] wlp1s0: Limiting TX power to 0 (-128 - 0) dBm as advertised by 86:3f:70:b9:12:51
[ 104.251222] ucsi_acpi USBC000:00: ucsi_handle_connector_change: ACK failed (-110)
[ 109.883208] ucsi_acpi USBC000:00: ucsi_handle_connector_change: ACK failed (-110)
[ 127.210913] warning: `kded5' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
--
[ 139.495639] Freezing remaining freezable tasks completed (elapsed 0.000 seconds)
[ 139.495642] printk: Suspending console(s) (use no_console_suspend to debug)
[ 139.503993] queueing ieee80211 work while going to suspend
--
[ 1107.007488] nvme nvme0: 16/0/0 default/read/poll queues
[ 1107.146946] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
[ 1107.147033] [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
[ 1107.149051] [drm] PCIE GART of 512M enabled (table at 0x000000801FD00000).
--
[ 1110.306441] usb 1-4: reset full-speed USB device number 2 using xhci_hcd
[ 1112.465146] ucsi_acpi USBC000:00: ucsi_handle_connector_change: ACK failed (-110)
[ 1118.097122] ucsi_acpi USBC000:00: ucsi_handle_connector_change: ACK failed (-110)
[ 1150.492745] wlp1s0: authenticate with 2a:0f:74:4c:6c:8e
I’ll drop some more interesting findings later tonight
9 Likes
So this is also effecting the UFI menus where even in the bootloader performance lags. I don’t want to use fedora, Seeing how this is effecting both environments (In windows I updated to the latest driver package and these issues still persist)
I have a similar problem, when I close the lid while it’s still connected to the charger and it goes to suspend, and I then unplug the charger, it then also wakes up again (I can also see the screen light turning on through a thin gap). It’s only the charger connected and then unplugged, not a dock.
I’m still on the old BIOS, and I can also reproduce your wake-on-close problem there, so that’s both nothing really related to the new BIOS version (I assume that the wake-on-unplug also still happens with the new BIOS?). But both shouldn’t happen, the laptop shouldn’t wake up when closed.
2 Likes
Noticed this today too on ubuntu22.04 oem kernel.
(also,resuming from suspend lead to a white screen, no way to recover from it, only the cursor is visible)
1 Like
Alright, status update. It’s an EC bug. I thought I read once that the Framework EC firmware was/would-be open-source? I think the EC should be more configurable.
This fixes the problem but then you can’t wake the PC up again
echo "Y" | sudo tee /sys/module/acpi/parameters/ec_no_wakeup
Disabling everything in /proc/acpi/wakeup doesn’t prevent wakeups, only ec_no_wakeup but that disables everything including the power button
We’re getting ready to pull this out of beta, so I need to make sure I have everything straight.
- Those seeing suspend wakeups (as I am not on either of my AMD Ryzen 7040 laptops), what is attached and what was running? On my test machines, lid close is suspend to RAM (on our tested and recommended distributions) and resume takes place on lid open events.
Thanks