6.5.7-t2 does not wake from suspend #53

aboulfad · 2023-10-18T12:18:25Z

Issue
MacBook Pro (MBP) always freezes/crashes when using suspend in Linux-t2-ubuntu. This is evident when re-starting, the boot screen shows fsck (or equivalent) running as well as the MBP bong & login to Linux. I included dmesg log as well screenshot from boot process.

MBP Info
MacBook Pro 2018, i7
Model ID: MacBookPro15,2
Controller Firmware version: 21P365
OS: Sonoma (14.0)

T2Linux Info
kernel: 6.5.7-t2
OS: Ubuntu 23.10 (Mantic Minotaur)

dmesg.log

AdityaGarg8 · 2023-10-18T12:38:23Z

Suspend has been broken since macOS Sonoma

aboulfad · 2023-10-18T13:51:14Z

Thanks, should I keep this issue open ? For other who may have trouble with this, in the meantime the behavior can be changed for lid close = ignore or lock. reference

AdityaGarg8 · 2023-10-18T13:55:57Z

Can be kept open

rydymth · 2023-11-13T06:32:07Z

Hi there!,
I am having a similar problem but for some reason, before apple decided to screw up the wifi and bluetooth firmware packages with the macos sonoma, i believe i have taken a backup of the previous firmware packages. You can download from here.
I am yet to figure out a way to do these things. With the latest kernel that is 6.6 something, my bluetooth stops working so i go back to previous kernel that was working very well for me before sonoma that was 6.3.6.
I will keep on trying to get my suspend working. I think ill replace my current OS with a new one with the older kernel.
Ill update if this worked for me.

AdityaGarg8 · 2023-11-13T06:45:09Z

I guess there is a regression in kernel 6.5 that broke Bluetooth for some models. Can you see if you get Bluetooth working on a 6.4.x and a 6.5 kernel @rydymth

rydymth · 2023-11-13T12:10:05Z

Hi!
The bluetooth works on all 6.4.* kernel. I tested on 6.4.7 and 6.4.8. It works just fine.
It however doesnt work on 6.5.*. I have tested on 6.5.2 and 6.5.8...
And it does not work on 6.6.1 either...

AdityaGarg8 · 2023-11-13T12:28:26Z

Can you share your complete journalctl -k from a 6.4 and 6.5 kernel. You can use pastebin to share

rydymth · 2023-11-13T20:29:46Z

HI!
Yes for sure!
Here is the journalctl for linux6.4.8 where everythin works except suspend.
And here is the journalctl for linux6.5.2 where bluetooth and suspend are not working.
There is an array index out of bounds error in both of them. Im not able to understand much but will attempt to debug more. There is a reference to this: try_to_wake_up+0x292/0x6c0 in the stack trace. Would this be the issue?
I am unable to find why bluetooth isnt working in the 6.5.2 one...

AdityaGarg8 · 2023-11-13T20:58:25Z

I've filed a bug report upstream:

https://lkml.org/lkml/2023/11/13/722

AdityaGarg8 · 2023-11-14T07:17:45Z

Hi @rydymth

Kernel 6.6.1-2 has a patch sent by upstream maintainers to fix Bluetooth on your model. Can you give it a test when it compiles. It should compile after 2.5-3hrs after I send this message.

rydymth · 2023-11-14T08:56:31Z

Hi @AdityaGarg8!
Just tried the new commit. Still no luck...
It is showing this error everytime i try to load/reload the hci_bcm4377 module:
[ 386.052230] hci_bcm4377 0000:73:00.1: can't disable ASPM; OS doesn't have ASPM control
Dmesg Log Link
Journalctl Log Link

aboulfad · 2023-11-14T09:00:01Z

Hi, I am a bit confused as to how @rydymth BT’s issue is related to the suspend issue I reported ? Thanks.

AdityaGarg8 · 2023-11-14T09:01:02Z

Hi, I am a bit confused as to how @rydymth BT’s issue is related to the suspend issue I reported ? Thanks.

Its not related to suspend, but is an issue that deserves to be fixed

aboulfad · 2023-11-14T09:06:16Z

Ok, I guess @rydymth could have created another GH issue, hence my confusion.

AdityaGarg8 · 2023-11-14T09:09:14Z

Hi @AdityaGarg8! Just tried the new commit. Still no luck... It is showing this error everytime i try to load/reload the hci_bcm4377 module: [ 386.052230] hci_bcm4377 0000:73:00.1: can't disable ASPM; OS doesn't have ASPM control Dmesg Log Link Journalctl Log Link

Looks like the UBSAN error got fixed. Got another patch, try 6.6.1-3

rydymth · 2023-11-14T14:19:17Z

Yes UBSAN error is fixed. For the ASPM error i put pcie_aspm=off pcie_port_pm=off in grub's GRUB_CMDLINE_LINUX.
But bluetooth still isnt working and suspend is still the same.
Here is the dmesg and the journalctl
I zgree with you @aboulfad I should create another issue indeed but hear me out.
I believe suspend has some relation to bluetooth not working and the buggy brcmfmac_wcc module. I blieve this is because of the updated macos firmware. When i tried to suspend on the live environment without installing the firmware.tar.gz, it suspended just fine no problem. I forgot to take the dmesg from that, will take the dmesg tonight.
So then i booted into 6.4.8 and this latest one 6.6.1-3 and i use this rmmod.sh script to remove the wifi and bluetooth modules via this script so that while suspend the wifi/bluetooth dont get in the way.
Here is the code:

#!/usr/bin/env bash
if [ "${1}" = "pre" ]; then
systemctl stop NetworkManager
modprobe -r brcmfmac_wcc brcmfmac hci_bcm4377
dmesg >> /home/rudy/logs/suspendPre.txt
elif [ "${1}" = "post" ]; then
modprobe brcmfmac_wcc brcmfmac hci_bcm4377
dmesg >> /home/rudy/logs/suspendPost.txt
systemctl start NetworkManager
fi

It shuts the display and i believe it suspends tasks and processes just fine. I have the USB-C connector attached to this laptop and while the screen is off the light on the USB-C connector still lights up, thats how i know my macbook didnt shut itself down.
So thats why i piped the dmesg right before suspend and right after suspend.
The post suspend did not update.
However this is the pre suspend log.
It says it suspends and then our brcmfmac driver doesnt sleep and then it resumes but then it never shows up on screen. My laptop always gets back up if i dont do the modprobe -r brcmfmac_wcc brcmfmac hci_bcm4377 either on the terminal or on rmmod.sh.
But here it doesnt.
I dont understand whats going on here.
Bluetooth isnt being discovered at all. Using bluetoothctl show, i get this No default controller available. So maybe the bluetooth isnt related to the suspend?
So should i open a new issue for bluetooth @AdityaGarg8 ?

AdityaGarg8 · 2023-11-14T14:22:46Z

Suspend is related to apple-bce so please don't mix it with Bluetooth.

But cause your Bluetooth issue has been introduced here, let it be here

AdityaGarg8 · 2023-11-14T14:24:38Z

I would prefer a log without the ASPM parameters you added and before suspending.

AdityaGarg8 · 2023-11-14T14:25:51Z

Suspend may break Bluetooth, but rn the priority is to make it working before suspending.

aboulfad · 2023-11-14T14:33:09Z

No worries @rydymth , I was trying to find some correlation or understanding, thanks.

rydymth · 2023-11-15T06:42:27Z

Suspend is related to apple-bce so please don't mix it with Bluetooth.

But cause your Bluetooth issue has been introduced here, let it be here

Got It!
Removed the ASPM parameters.
Here are the Dmesg, journalctl and preSuspend

AdityaGarg8 · 2023-11-15T06:45:48Z

So no errors, but Bluetooth still broken?

rydymth · 2023-11-15T06:47:07Z

Yes...
No errors
But no luck with bluetooth...

AdityaGarg8 · 2023-11-15T06:48:05Z

Is journalctl you sent post suspend?

AdityaGarg8 · 2023-11-15T06:48:16Z

And what is presuspend

rydymth · 2023-11-15T06:52:47Z

Is journalctl you sent post suspend?

No, This is journalctl normally after booting up.

And what is presuspend

This one is just a scirpt i wrote above. Before going to suspend i put the dmesg into this preSuspend.txt. So everytime i do systemctl suspend the dmesg gets is written to the file. In the scrpit i also have written the postSuspend script but that doesnt work...

AdityaGarg8 · 2023-11-15T06:59:07Z

Why your journalctl does not have the kernel parameters.

I want journalctl -k after you boot and attempt to start Bluetooth. Probably run sudo modprobe -r brcmfmac_wcc; sudo modprobe -r brcmfmac; sudo modprobe -r hci_bcm4377; sudo modprobe hci_bcm4377 then share journalctl -k

AdityaGarg8 · 2023-11-15T07:00:05Z

And please, no suspend

AdityaGarg8 · 2023-11-15T07:00:50Z

I need to talk to upstream, so would prefer keeping suspend out of this. Suspend is an issue which we need to handle, not upstream.

rydymth · 2023-11-15T07:16:07Z

I need to talk to upstream, so would prefer keeping suspend out of this. Suspend is an issue which we need to handle, not upstream.

Got it
Here is the journalctl -k and the dmesg after removing and loading the brcmfmac_wcc brcmfmac and hci_bcm4377 modules.

AdityaGarg8 · 2024-01-02T04:27:56Z

I want to mention that I am facing this issue too on my 2018 Intel T2 MacBook Air. I use the latest LTS Ubuntu and everything works including wifi and bluetooth but not the suspend on lid close https://mdsheraj123.github.io/2023/11/11/Installing-Ubuntu-22.04-LTS-on-a-Intel-MacBook-air-2018-with-T2-chip/html. This is a problem because I have assigned lid close to lock my screen and often forget to manually shut down. This leads to my battery draining out when I reopen my laptop making it unreliable and losing the charm of the MacBook battery life.

If this is fixed, I won't buy a dedicated Linux laptop.

I don't find suspend getting fixed anytime soon. Also, the camera fix in your article is not relevant at all.

mdsheraj123 · 2024-01-07T22:39:41Z

My MacBook webcam was not working and https://devicetests.com/fix-webcam-issues-ubuntu-macbook-air actually fixed my webcam. It worked for me.

MacBooks are popular and last a long time. Linux support on MacBooks will definitely boost Linux adoption. Although, yes, open source hardware is the best. I hope for the suspend fix for my current daily driver.

nicovell3 · 2024-01-12T08:28:23Z

I'm currently affected by this issue in a MacBook I've recently acquired, with Sonoma installed. Is there any way to downgrade my running MacOS to get the sleep and bluetooth features working? Which was the latest working version?

AdityaGarg8 · 2024-01-12T08:29:42Z

Even if you downgrade, the sleep issue won't get fixed. People have got success with s2idle sleep, you can try that.

aboulfad · 2024-01-12T10:50:31Z

You can search in the discord general channel « s2idle », I think it works for some & not others & it isn’t true deep sleep so battery consumption may still be an issue. I haven’t tried it yet as I am rarely using Ubuntu on my MBP 2018.

echo freeze | sudo tee /sys/power/state

nicovell3 · 2024-01-12T12:33:43Z

S2 will not be enough to have the MBP disconnected for many hours... Maybe a solution could be to have it configured to hibernate after a few minutes. I hope this suspend issue gets fixed.

Simon-Martens · 2024-02-01T18:48:10Z

Does not work for me, either.

Macbook Pro 2018 15,1
Hybrid graphics with an Radeon Pro 555X
Kernel: Linux 6.6.8-t2-mantic (on Ubuntu 23.10)

This seems like a hard one, bc after trying to wake the macbook from deep sleep, it does not turn on the screen or log any messages (?? if it was bce_vhci it would at least be able to write something to the disk or am I mistaken here??); although something appears to be happening:

In a suspended state I press any key to wake the macbook
The touchbar turns on, but is non responsive.
5-10 seconds nothing else happens, screen is black.
The fans start spinning for a second and the laptop is shut down (sometimes i have to manually shut it down pressing the power button, after waiting a bit).

S2Idle does not work for me, same behavior (maybe I need to switch to Intel graphics, haven't tried it yet).

Hibernation (suspend to disk) also doesn't work, since bce_vhci does not resume, so touchpad & keyboard won't work (but I think it might be a different issue).

I can not confirm @aboulfad s findings since if I blacklist all the modules suspend shows the exact same behavior.

EDIT: If somebody needs any help debugging this, recompiling an testing a module etc etc I've got time and motivation to do it :)

AdityaGarg8 · 2024-02-02T05:24:46Z

I've noticed s2idle works only with Intel GPU.

aboulfad · 2024-02-02T10:43:22Z

I've noticed s2idle works only with Intel GPU.

Sadly, not on my 2018 MBP i7 (Intel Iris Plus Graphics 655), s2idle also results in a frozen system requiring a hard reset.

Simon-Martens · 2024-02-02T15:47:17Z

I can confirm, still not working when setting my Intel UHD Graphics 630 as the main graphics and blacklisting the amdgpu kernel module. Maybe it's macbooks with ONLY integrated GPUs, like many 13 inch models? Can somebody with a working s2idle state post system configuration / specs? Maybe also a boot log?

Maybe it would be helpful to compare boot logs of a working (old firmware?) system in general, since there are some ACPI errors in mine; and given the system doesn't boot enough to even log anything it could be some power management issue.

Also apple_bce resumes normally if the suspend is aborted just before power off (sometimes the wifi card does prevent suspending, but this is also a seperate issue I think). apple_bce shuts down, then resumes correctly in that case, when power was not fully off.

AdityaGarg8 · 2024-02-02T15:58:23Z

Contact the discord if you want to chat with people who have this working.

aboulfad · 2024-02-02T16:03:08Z

@Simon-Martens s2idle doesn’t work on my 2018 MBP 13” intel integrated gpu only. I’ve already checked many of the discord suggestions to no avail, good luck for your setup.

riddlework · 2024-04-01T21:29:25Z

Have there been any updates to this issue in the last two months? I have a 16' 2019 MBP with BRCM Wi-Fi card and AMD graphics card and have been troubleshooting this issue all weekend to no avail.

AdityaGarg8 · 2024-04-02T00:49:36Z

Have there been any updates to this issue in the last two months? I have a 16' 2019 MBP with BRCM Wi-Fi card and AMD graphics card and have been troubleshooting this issue all weekend to no avail.

Not yet

POMATu · 2024-04-29T00:23:18Z

dmesg.log
hi everyone, while its not suspend, i was somehow able to make it hibernate. Neither was working for me before.
I edited /etc/systemd/sleep.conf and found out that there is some "shutdown type" for hibernation

[Sleep]
AllowSuspend=no
AllowHibernation=yes
#AllowSuspendThenHibernate=yes
AllowHybridSleep=no
#SuspendMode=
#SuspendState=mem standby freeze
#HibernateMode=platform shutdown
HibernateMode=shutdown
HibernateState=disk
#HybridSleepMode=suspend platform shutdown
#HybridSleepState=disk
#HibernateDelaySec=
#SuspendEstimationSec=60min

I also blocked non-working suspend. I had resume kernel arguments preset in grub cmdline before and it actually worked. It was able to save image, then turn off properly without reset, then i booted it back and it actually restored image
Just few issues make system unusable:

internal macbook keyboard not working, but external USB does work, thats how i was able to unlock lockscreen
touchbar completely dead
wifi ping working from macbook but i cant connect SSH to macbook for some reason, it drops connection straight after banner and i wasnt able to use ssh until i rebooted. The issue was same on ethernet cable and on wifi. I collected dmesg tho, it said it restored from hibernation, didnt see much errors

Is it worth trying to make it work further? It seems issues are related to some frozen ACPI modules. Can you kindly tell me what modules can I unload and reload or what else can i try to make system usable after restore from hibernation.

My grub cmdline:
GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on iommu=pt pcie_ports=compat resume=UUID=61787ea2-d76f-4e2d-94d7-be27c37cf26f resume_offset=35284992 init_on_alloc=0 apple_set_os"

Linux macbookpro 6.8.8-t2 #1 SMP PREEMPT_DYNAMIC Sun Apr 28 07:27:07 UTC 2024 x86_64 GNU/Linux
Debian 12

Thanks

UPD: And i cant repeat it... on top of that my touchbar not going back even across reboots, like its still some tainted boot that i cant cleanse. Thats strange: it gave me hope and now doing same thing again. Well not exact same thing: now it just wakes up instantly instead of going to hibernation.

UPD2: I am able to put it to hibernation again, i just have to type touchpad --restart first so touchpad starts working and then hibernation doesnt gets cancelled with systemctl hibernate. But still after restore of state I am unable to make keyboard and touchpad and touchbar to work. Hibernation could be nice alternative if its possible to make these modules work
BTW dropbear luks unlock works just fine keyboard stops working later (when it actually restores image from swap)

AdityaGarg8 · 2024-04-29T16:06:09Z

dmesg.log hi everyone, while its not suspend, i was somehow able to make it hibernate. Neither was working for me before. I edited /etc/systemd/sleep.conf and found out that there is some "shutdown type" for hibernation
[Sleep]
AllowSuspend=no
AllowHibernation=yes
#AllowSuspendThenHibernate=yes
AllowHybridSleep=no
#SuspendMode=
#SuspendState=mem standby freeze
#HibernateMode=platform shutdown
HibernateMode=shutdown
HibernateState=disk
#HybridSleepMode=suspend platform shutdown
#HybridSleepState=disk
#HibernateDelaySec=
#SuspendEstimationSec=60min
I also blocked non-working suspend. I had resume kernel arguments preset in grub cmdline before and it actually worked. It was able to save image, then turn off properly without reset, then i booted it back and it actually restored image Just few issues make system unusable:

internal macbook keyboard not working, but external USB does work, thats how i was able to unlock lockscreen

touchbar completely dead

wifi ping working from macbook but i cant connect SSH to macbook for some reason, it drops connection straight after banner and i wasnt able to use ssh until i rebooted. The issue was same on ethernet cable and on wifi. I collected dmesg tho, it said it restored from hibernation, didnt see much errors

Is it worth trying to make it work further? It seems issues are related to some frozen ACPI modules. Can you kindly tell me what modules can I unload and reload or what else can i try to make system usable after restore from hibernation.

My grub cmdline: GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on iommu=pt pcie_ports=compat resume=UUID=61787ea2-d76f-4e2d-94d7-be27c37cf26f resume_offset=35284992 init_on_alloc=0 apple_set_os"

Linux macbookpro 6.8.8-t2 #1 SMP PREEMPT_DYNAMIC Sun Apr 28 07:27:07 UTC 2024 x86_64 GNU/Linux Debian 12

Thanks

UPD: And i cant repeat it... on top of that my touchbar not going back even across reboots, like its still some tainted boot that i cant cleanse. Thats strange: it gave me hope and now doing same thing again. Well not exact same thing: now it just wakes up instantly instead of going to hibernation.

UPD2: I am able to put it to hibernation again, i just have to type touchpad --restart first so touchpad starts working and then hibernation doesnt gets cancelled with systemctl hibernate. But still after restore of state I am unable to make keyboard and touchpad and touchbar to work. Hibernation could be nice alternative if its possible to make these modules work BTW dropbear luks unlock works just fine keyboard stops working later (when it actually restores image from swap)

Interesting finding, but the issue you are facing is most likely due to apple-bce. Do you have any logs from apple-bce after resuming?

POMATu · 2024-04-29T17:45:28Z

Interesting finding, but the issue you are facing is most likely due to apple-bce. Do you have any logs from apple-bce after resuming?

since now i am able to repeat the process i can collect any kind of logs. Where are the apple-bce logs if its not dmesg? Dmesg after restore i did already provide above.

AdityaGarg8 · 2024-04-29T18:05:19Z

Interesting finding, but the issue you are facing is most likely due to apple-bce. Do you have any logs from apple-bce after resuming?

since now i am able to repeat the process i can collect any kind of logs. Where are the apple-bce logs if its not dmesg? Dmesg after restore i did already provide above.

Probably check journalctl

[ 232.734819] bce-vhci: Possible desync, cmd cancel timed out

This was in your dmesg, indicates its bce at fault. Nothing can be done here.

POMATu · 2024-04-30T18:14:53Z

i booted today with macbook connected to external keyboard and monitor and touchbar was working straight away i didnt have to restart it.
Then i hibernated and restored and collected both logs:
30apr-dmesg.log
journalctl-30apr.log
I have done nothing else on linux today and system is utterly unconfigured and vanilla so logs should be clean from garbage.
And now I uploaded logs via actual working system. If i am using external keyboard and monitor - system is 100% usable, no issues with wifi, just as i said before: touchbar, internal keyboard dont work

Apr 30 14:05:15 macbookpro kernel: bce_vhci: suspend started
Apr 30 14:05:15 macbookpro kernel: bce_vhci: suspend endpoints
Apr 30 14:05:15 macbookpro kernel: bce-vhci: Not implemented: wait for pending output requests
Apr 30 14:05:15 macbookpro kernel: bce-vhci: Not implemented: wait for pending output requests
Apr 30 14:05:15 macbookpro kernel: bce_vhci: suspend ports
Apr 30 14:05:15 macbookpro kernel: bce_vhci: suspend controller
Apr 30 14:05:15 macbookpro kernel: bce_vhci: suspend done
Apr 30 14:05:15 macbookpro kernel: bce_vhci: resume started
Apr 30 14:05:15 macbookpro kernel: bce_vhci: resume controller
Apr 30 14:05:15 macbookpro kernel: bce-vhci: Possible desync, cmd cancel timed out
Apr 30 14:05:15 macbookpro kernel: bce-vhci bce-vhci: HC died; cleaning up
Apr 30 14:05:15 macbookpro kernel: cdc_ncm 7-1:1.0 enxacde48001122: unregister 'cdc_ncm' usb-bce-vhci-1, CDC NCM (NO ZLP)
Apr 30 14:05:15 macbookpro kernel: bce_vhci_drop_endpoint 1:1
Apr 30 14:05:16 macbookpro PackageKit[1522]: search-file transaction /1026_bcdcbcea from uid 1000 finished with success after 275ms
Apr 30 14:05:20 macbookpro PackageKit[1522]: get-details transaction /1037_abceeeec from uid 1000 finished with success after 240ms
Apr 30 14:05:21 macbookpro kernel: bce-vhci: Possible desync, cmd cancel timed out

Are these the logs you wanted to see?

POMATu · 2024-05-02T01:12:22Z

i just found my macbook inside my bag hot af because i closed it and forgot to poweroff. Luckily it seems nothing bad happened this time but it proves that this issue is really painful and my lid-closing habits can actually ruin the hardware.
Some people in this thread proposed to disable action on lid closure, but it seems i have to enable some sort of powering off or it will happen again. Someone else proposed switching it off on lid closure but then you will loose not-saved data if you did it by accident.
Hence I think this "shutdown type" hibernation is good compromise in terms of both having some action that turns it off (so it doesnt overheats in bag) and saving the data, that you can at least recover with usb mouse or even android phone as HID controller.

While i am still hoping for a possibility to make hibernation work with some crutch that resets those frozen modules after RAM image restore, but for now I will live with currently posted shutdown-type hibernation method because it both does action on lid closure and saves the data currently in RAM.

One important thing to add to my previous post:
I think its mandatory to have touchbar --restart somewhere late after boot, in desktop environment startup file and maybe in /etc/rc.local too just in case it wasnt unlocked yet, because sometimes touchbar doesnt starts for me randomly and if it doesnt starts then my hibernation method cancels instead of doing shutdown and then i might get hot bag issue again. Anyways thats just a backup for the situation when i forgot to turn it off normally.

rydymth · 2024-06-09T19:35:59Z

I also blocked non-working suspend. I had resume kernel arguments preset in grub cmdline before and it actually worked. It was able to save image, then turn off properly without reset, then i booted it back and it actually restored image
Just few issues make system unusable:
internal macbook keyboard not working, but external USB does work, thats how i was able to unlock lockscreen

I was able to follow through this and am getting the same exact problem that you are facing @POMATu ! But my wifi and bluetooth works and i am able to ssh into my system as well.
For me the s2Idle sleep works but drains a lot of battery and for some reason my laptop gets heated at times...
I think its just like @AdityaGarg8 said its an apple_bce error.

stereo4nick · 2024-06-15T19:23:04Z

Hi guys. Recently bought used mba 2020 i5 for ubuntu and googled t2 project. This is awesome and thank you for this gem.
As ppl said in above I'm also can't reach suspend/hibernate. Here is my uname -a
Linux mba 6.9.4-1-t2-jammy #1 SMP PREEMPT_DYNAMIC Wed Jun 12 17:36:21 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
and journalctl logs for suspend/hib

hibernate.log
suspend.log

Maybe this will help when you'll have a time.

Some additional things to say.

Tried 24.04 but noticed more power consumtion than 22.04. So preferring 22.04
Unfortunately before figured out I updated my mba to sonoma but rolled back it to monterey for no reason. I grabbed firmware for myself from macos' 11,12,13. Right now 22.04 use 12's firmware but same behavior on 13's firmware, it seems 11's is not supported.
Switched handling closed lid to lock screen, with my 900 cycles bat it won't last long ~20h from 100% to empty. Tried to hibernate but no luck. It looks like system go to sleep: display and backlit turns off but after 10-15 sec it wake up without working keyboard and touchpad. Here is my /etc/systemd/sleep.conf:

[Sleep]
AllowSuspend=no
AllowHibernation=yes
#AllowSuspendThenHibernate=yes
AllowHybridSleep=no
#SuspendMode=
#SuspendState=mem standby freeze
HibernateMode=shutdown
HibernateState=disk
#HybridSleepMode=suspend platform shutdown
#HybridSleepState=disk
#HibernateDelaySec=180min

followed this instruction for setup swapfile https://linuxhint.com/enable-hibernate-ubuntu-22-04-lts/
probably in t2 kernels has some different settings for hibernate because of it wakes up after ~15 sec?
4. OS wakes up after several seconds (more faster than hib) from suspend. Sometimes wifi works but sometimes there is empty wifi list because of broken brcm I guess which can be reloaded with modprobe -r hci_bcm4377 ...
5. Tried to disable all items in /proc/acpi/wakeup because noticed in log
Jun 15 12:36:06 mba kernel: PM: Some devices failed to suspend, or early wake event detected
but no luck

Really hope suspend/hib will addressed eventually otherwise I have to run my dev environment/docker every day 🙂 and I see no other workaround.

AdityaGarg8 · 2024-06-16T03:42:31Z

Hi guys. Recently bought used mba 2020 i5 for ubuntu and googled t2 project. This is awesome and thank you for this gem. As ppl said in above I'm also can't reach suspend/hibernate. Here is my uname -a Linux mba 6.9.4-1-t2-jammy #1 SMP PREEMPT_DYNAMIC Wed Jun 12 17:36:21 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux and journalctl logs for suspend/hib

hibernate.log suspend.log

Maybe this will help when you'll have a time.

Some additional things to say.

Tried 24.04 but noticed more power consumtion than 22.04. So preferring 22.04

Unfortunately before figured out I updated my mba to sonoma but rolled back it to monterey for no reason. I grabbed firmware for myself from macos' 11,12,13. Right now 22.04 use 12's firmware but same behavior on 13's firmware, it seems 11's is not supported.

Switched handling closed lid to lock screen, with my 900 cycles bat it won't last long ~20h from 100% to empty. Tried to hibernate but no luck. It looks like system go to sleep: display and backlit turns off but after 10-15 sec it wake up without working keyboard and touchpad. Here is my /etc/systemd/sleep.conf:
[Sleep]
AllowSuspend=no
AllowHibernation=yes
#AllowSuspendThenHibernate=yes
AllowHybridSleep=no
#SuspendMode=
#SuspendState=mem standby freeze
HibernateMode=shutdown
HibernateState=disk
#HybridSleepMode=suspend platform shutdown
#HybridSleepState=disk
#HibernateDelaySec=180min
followed this instruction for setup swapfile https://linuxhint.com/enable-hibernate-ubuntu-22-04-lts/ probably in t2 kernels has some different settings for hibernate because of it wakes up after ~15 sec? 4. OS wakes up after several seconds (more faster than hib) from suspend. Sometimes wifi works but sometimes there is empty wifi list because of broken brcm I guess which can be reloaded with modprobe -r hci_bcm4377 ... 5. Tried to disable all items in /proc/acpi/wakeup because noticed in log Jun 15 12:36:06 mba kernel: PM: Some devices failed to suspend, or early wake event detected but no luck

Really hope suspend/hib will addressed eventually otherwise I have to run my dev environment/docker every day 🙂 and I see no other workaround.

There was not point to reverting back to Monterey. Just keep your Mac updated now. Wi-Fi firmware has no role in suspend.

For Wi-Fi issues, your Mac model has broken Bluetooth driver with interferes with Wi-Fi. Prefer using a 5Ghz Wi-Fi or just blacklist Bluetooth driver if you don't need it.

angelobdev · 2024-06-16T10:23:27Z

So I made a few tests using this apple-bce-drv fork...

Following this guide I retrieved these results:

Resume failed, dmesg after reboot:

[    0.304723] PM:   Magic number: 12:311:243
[    0.304766] acpi device:86: hash matches

Following this guide I retrieved these results:

core: failed

[    0.308562] PM:   Magic number: 12:520:346
[    0.308579] tty tty63: hash matches

processors: failed

[    0.305757] PM:   Magic number: 12:967:295
[    0.305775] tty tty28: hash matches

platform: failed

[    0.316095] PM:   Magic number: 12:314:144
[    0.316136] acpi device:15: hash matches

devices: success
dmesg_devices.txt

freezer: success
dmesg_freezer.txt

Still unknown what's causing the panic.

NOTE:

freezer
- test the freezing of processes

devices
- test the freezing of processes and suspending of devices

platform
- test the freezing of processes, suspending of devices and platform
  global control methods(*)

processors
- test the freezing of processes, suspending of devices, platform
  global control methods(*) and the disabling of nonboot CPUs

core
- test the freezing of processes, suspending of devices, platform global
  control methods(*), the disabling of nonboot CPUs and suspending of
  platform/system devices

(*) the platform global control methods are only available on ACPI systems
    and are only tested if the hibernation mode is set to "platform"

From: https://www.kernel.org/doc/Documentation/power/basic-pm-debugging.txt

POMATu · 2024-07-09T10:47:54Z

I was able to follow through this and am getting the same exact problem that you are facing @POMATu ! But my wifi and bluetooth works and i am able to ssh into my system as well. For me the s2Idle sleep works but drains a lot of battery and for some reason my laptop gets heated at times... I think its just like @AdityaGarg8 said its an apple_bce error.

Hey i want to clarify few points in this thread for the people that landed here from search engine, because it was utterly unclear for me at the time i found this thread, that time i thought i gotta use my macbook without suspend working, but its not true:

You can actually have suspend working in some distros with suspend workaround here:
https://wiki.t2linux.org/guides/postinstall/#suspend-workaround and by using latest t2 kernels
I got it working on my debian and it works on arch and maybe somewhere else too. This workaround just adds extra latency to suspend+restore but it works, you can actually close lid and put it to bag and then take out and open it back like normal and have somewhat normal non-disabled linux on laptop experience
You might get better help and faster response on discord server, so if you are googling solution to your problem you might wanna go there and ask. I randomly decided to join discord server and realized that i should've done that from the start

stereo4nick · 2024-07-10T22:11:47Z

I was able to follow through this and am getting the same exact problem that you are facing @POMATu ! But my wifi and bluetooth works and i am able to ssh into my system as well. For me the s2Idle sleep works but drains a lot of battery and for some reason my laptop gets heated at times... I think its just like @AdityaGarg8 said its an apple_bce error.

Hey i want to clarify few points in this thread for the people that landed here from search engine, because it was utterly unclear for me at the time i found this thread, that time i thought i gotta use my macbook without suspend working, but its not true:

You can actually have suspend working in some distros with suspend workaround here:
https://wiki.t2linux.org/guides/postinstall/#suspend-workaround and by using latest t2 kernels
I got it working on my debian and it works on arch and maybe somewhere else too. This workaround just adds extra latency to suspend+restore but it works, you can actually close lid and put it to bag and then take out and open it back like normal and have somewhat normal non-disabled linux on laptop experience

You might get better help and faster response on discord server, so if you are googling solution to your problem you might wanna go there and ask. I randomly decided to join discord server and realized that i should've done that from the start

Hi! Unfortunately that workaround isn't working for my mba 2020 on ubuntu 6.9.8-3-t2-jammy.
It looks like system is going to sleep (instead immediately wake up) but unable to wakeup.
I know about workaround work only for Arch.
This is my suspend-fix-t2.service (I'm not sure about commands is correct)

`
[Unit]
Description=Disable and Re-Enable Apple BCE Module (and Wi-Fi)
Before=sleep.target
StopWhenUnneeded=yes

[Service]
User=root
Type=oneshot
RemainAfterExit=yes

ExecStart=modprobe -r brcmfmac_wcc
ExecStart=modprobe -r brcmfmac
#ExecStart=/usr/bin/rmmod -f apple-bce
#ExecStart=rmmod -f apple-bce
ExecStart=modprobe apple-bce

ExecStop=modprobe apple-bce
ExecStop=modprobe brcmfmac
ExecStop=modprobe brcmfmac_wcc

[Install]
WantedBy=sleep.target
`

for commented rows I got errors:

suspend-fix-t2.service: Failed at step EXEC spawning /usr/bin/rmmod: No such file or directory Subject: Process /usr/bin/rmmod could not be executed

...

Jun 11 02:44:04 mba rmmod[3681]: rmmod: ERROR: ../libkmod/libkmod-module.c:799 kmod_module_remove_module() could not remove 'apple_bce': Resou> Jun 11 02:44:04 mba rmmod[3681]: rmmod: ERROR: could not remove module apple-bce: Resource temporarily unavailable Jun 11 02:44:04 mba systemd[1]: suspend-fix-t2.service: Main process exited, code=exited, status=1/FAILURE ░░ Subject: Unit process exited

AdityaGarg8 · 2024-07-11T04:23:12Z

I was able to follow through this and am getting the same exact problem that you are facing @POMATu ! But my wifi and bluetooth works and i am able to ssh into my system as well. For me the s2Idle sleep works but drains a lot of battery and for some reason my laptop gets heated at times... I think its just like @AdityaGarg8 said its an apple_bce error.

Hey i want to clarify few points in this thread for the people that landed here from search engine, because it was utterly unclear for me at the time i found this thread, that time i thought i gotta use my macbook without suspend working, but its not true:

You can actually have suspend working in some distros with suspend workaround here:
https://wiki.t2linux.org/guides/postinstall/#suspend-workaround and by using latest t2 kernels
I got it working on my debian and it works on arch and maybe somewhere else too. This workaround just adds extra latency to suspend+restore but it works, you can actually close lid and put it to bag and then take out and open it back like normal and have somewhat normal non-disabled linux on laptop experience

You might get better help and faster response on discord server, so if you are googling solution to your problem you might wanna go there and ask. I randomly decided to join discord server and realized that i should've done that from the start

Hi! Unfortunately that workaround isn't working for my mba 2020 on ubuntu 6.9.8-3-t2-jammy. It looks like system is going to sleep (instead immediately wake up) but unable to wakeup. I know about workaround work only for Arch. This is my suspend-fix-t2.service (I'm not sure about commands is correct)

` [Unit] Description=Disable and Re-Enable Apple BCE Module (and Wi-Fi) Before=sleep.target StopWhenUnneeded=yes

[Service] User=root Type=oneshot RemainAfterExit=yes

ExecStart=modprobe -r brcmfmac_wcc ExecStart=modprobe -r brcmfmac #ExecStart=/usr/bin/rmmod -f apple-bce #ExecStart=rmmod -f apple-bce ExecStart=modprobe apple-bce

ExecStop=modprobe apple-bce ExecStop=modprobe brcmfmac ExecStop=modprobe brcmfmac_wcc

[Install] WantedBy=sleep.target `

for commented rows I got errors:

suspend-fix-t2.service: Failed at step EXEC spawning /usr/bin/rmmod: No such file or directory Subject: Process /usr/bin/rmmod could not be executed

...

Jun 11 02:44:04 mba rmmod[3681]: rmmod: ERROR: ../libkmod/libkmod-module.c:799 kmod_module_remove_module() could not remove 'apple_bce': Resou> Jun 11 02:44:04 mba rmmod[3681]: rmmod: ERROR: could not remove module apple-bce: Resource temporarily unavailable Jun 11 02:44:04 mba systemd[1]: suspend-fix-t2.service: Main process exited, code=exited, status=1/FAILURE ░░ Subject: Unit process exited

I won't work for Ubuntu. Works only for Debian and Arch for now.

CaptainMorgan12 · 2024-09-07T13:56:49Z

The following seems to work at least the daemon does not complain, haven't tried to sleep it on Ubuntu 24.0.4.1 LTS without the linux-t2-lts kernel installed, kernel Linux 6.8.0-41-generic, MacPro 7,2.

[Unit]
Description=Disable and Re-Enable Apple BCE Module (and Wi-Fi)
Before=sleep.target
StopWhenUnneeded=yes

[Service]
User=root
Type=oneshot
RemainAfterExit=yes

ExecStart=/usr/sbin/modprobe -r brcmfmac_wcc
ExecStart=/usr/sbin/modprobe -r brcmfmac
#ExecStart=/usr/sbin/rmmod -f apple-bce
ExecStart=/usr/sbin/modprobe -r apple-bce

ExecStop=/usr/sbin/modprobe apple-bce
ExecStop=/usr/sbin/modprobe brcmfmac
ExecStop=/usr/sbin/modprobe brcmfmac_wcc

[Install]
WantedBy=sleep.target

systemctl daemon-reload

sudo systemctl restart suspend-fix-t2.service

systemctl status suspend-fix-t2.service

○ suspend-fix-t2.service - Disable and Re-Enable Apple BCE Module (and Wi-Fi)
     Loaded: loaded (/etc/systemd/system/suspend-fix-t2.service; enabled; preset: enabled)
     Active: inactive (dead) since Sat 2024-09-07 06:55:09 PDT; 5s ago
   Duration: 1ms
    Process: 82988 ExecStart=/usr/sbin/modprobe -r brcmfmac_wcc (code=exited, status=0/SUCCESS)
    Process: 82990 ExecStart=/usr/sbin/modprobe -r brcmfmac (code=exited, status=0/SUCCESS)
    Process: 82992 ExecStart=/usr/sbin/modprobe -r apple-bce (code=exited, status=0/SUCCESS)
    Process: 82994 ExecStop=/usr/sbin/modprobe apple-bce (code=exited, status=0/SUCCESS)
    Process: 83011 ExecStop=/usr/sbin/modprobe brcmfmac (code=exited, status=0/SUCCESS)
    Process: 83029 ExecStop=/usr/sbin/modprobe brcmfmac_wcc (code=exited, status=0/SUCCESS)
   Main PID: 82992 (code=exited, status=0/SUCCESS)
        CPU: 28ms

Sep 07 06:55:09 user systemd[1]: Starting suspend-fix-t2.service - Disable and Re-Enable Apple BCE Module (and Wi-Fi)...
Sep 07 06:55:09 user systemd[1]: Finished suspend-fix-t2.service - Disable and Re-Enable Apple BCE Module (and Wi-Fi).
Sep 07 06:55:09 user systemd[1]: Stopping suspend-fix-t2.service - Disable and Re-Enable Apple BCE Module (and Wi-Fi)...
Sep 07 06:55:09 user systemd[1]: suspend-fix-t2.service: Deactivated successfully.
Sep 07 06:55:09 user systemd[1]: Stopped suspend-fix-t2.service - Disable and Re-Enable Apple BCE Module (and Wi-Fi).

Tested and sortof works to wake from suspend, but is slow and only if you unplug and plugin:

keyboard (unplug, plugin, press key, wait, unpluck again, plug back in press key - external usb)
trackpad (external usb)
display (external apple thunderbolt)
log back in / re-connect network (ethernet internal)

if you just hit a keyboard button nothing happens. It does not seem to be watching correctly for keypresses.

sudo dmesg | grep error
[    6.058544] ACPI Error: Aborting method \_SB.PCI0.RP01.ARPT._PSW due to previous error (AE_TIME) (20230628/psparse-529)
[    8.558543] ACPI Error: Aborting method \_SB.PCI0.RP09.XGBE._PSW due to previous error (AE_TIME) (20230628/psparse-529)
[   11.058543] ACPI Error: Aborting method \_SB.PCI0.RP13.XGBE._PSW due to previous error (AE_TIME) (20230628/psparse-529)
[   13.571544] ACPI Error: Aborting method \_SB.PC04.MCP0.US00.DS09.UPSB.DSB2.XHC4._PSW due to previous error (AE_TIME) (20230628/psparse-529)
[   16.074547] ACPI Error: Aborting method \_SB.PC04.MCP0.US00.DS0A.UPSB.DSB2.XHC5._PSW due to previous error (AE_TIME) (20230628/psparse-529)
[   18.577545] ACPI Error: Aborting method \_SB.PC04.MCP0.US00.DS18.UPSB.DSB2.XHC2._PSW due to previous error (AE_TIME) (20230628/psparse-529)
[   21.079543] ACPI Error: Aborting method \_SB.PC04.MCP0.US00.DS19.UPSB.DSB2.XHC3._PSW due to previous error (AE_TIME) (20230628/psparse-529)
[   23.581545] ACPI Error: Aborting method \_SB.PC04.MCP0.US00.DS1A.UPSB.DSB2.XHC6._PSW due to previous error (AE_TIME) (20230628/psparse-529)
[   26.083543] ACPI Error: Aborting method \_SB.PC04.MCP0.US00.DS1B.UPSB.DSB2.XHC7._PSW due to previous error (AE_TIME) (20230628/psparse-529)
[   28.633548] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC._REG due to previous error (AE_TIME) (20230628/psparse-529)
[   28.646885] apple-properties: device path parse error -19 at 0x32:
[   28.646935] apple-properties: device path parse error -19 at 0x32:
[   44.168048] brcmfmac 0000:02:00.0: Direct firmware load for brcm/brcmfmac4364b3-pcie.apple,hanauma-HRPN-m-7.9-X0.bin failed with error -2
[   44.168113] brcmfmac 0000:02:00.0: Direct firmware load for brcm/brcmfmac4364b3-pcie.apple,hanauma-HRPN-m-7.9.bin failed with error -2
[   44.168215] brcmfmac 0000:02:00.0: Direct firmware load for brcm/brcmfmac4364b3-pcie.apple,hanauma-HRPN-m.bin failed with error -2
[   44.168257] brcmfmac 0000:02:00.0: Direct firmware load for brcm/brcmfmac4364b3-pcie.apple,hanauma-HRPN.bin failed with error -2
[   44.168311] brcmfmac 0000:02:00.0: Direct firmware load for brcm/brcmfmac4364b3-pcie.apple,hanauma-X0.bin failed with error -2
[   46.935450] pcieport 0000:12:00.0: AER: Correctable error message received from 0000:23:00.0
[   53.953869] pcieport 0000:12:00.0: AER: Uncorrectable (Non-Fatal) error message received from 0000:8a:02.0
[   53.953903] pcieport 0000:8a:02.0:   device [8086:15ea] error status/mask=00300000/00000000
[   53.965336] xhci_hcd 0000:8c:00.0: AER: can't recover (no error_detected callback)

journalctl -p 3 -xb
Sep 07 07:12:35 user kernel: ACPI Error: AE_TIME, Returned by Handler for [EmbeddedControl] (20230628/evregion-300)
Sep 07 07:12:35 user kernel: ACPI Error: Timeout from EC hardware or EC device driver (20230628/evregion-310)
Sep 07 07:12:35 user kernel: ACPI Error: Aborting method \_SB.PCI0.RP01.ARPT._PSW due to previous error (AE_TIME) (20230628/psparse-529)
Sep 07 07:12:35 user kernel: ACPI Error: AE_TIME, Returned by Handler for [EmbeddedControl] (20230628/evregion-300)
Sep 07 07:12:35 user kernel: ACPI Error: Timeout from EC hardware or EC device driver (20230628/evregion-310)
Sep 07 07:12:35 user kernel: ACPI Error: Aborting method \_SB.PCI0.RP09.XGBE._PSW due to previous error (AE_TIME) (20230628/psparse-529)
Sep 07 07:12:35 user kernel: ACPI Error: AE_TIME, Returned by Handler for [EmbeddedControl] (20230628/evregion-300)
Sep 07 07:12:35 user kernel: ACPI Error: Timeout from EC hardware or EC device driver (20230628/evregion-310)
Sep 07 07:12:35 user kernel: ACPI Error: Aborting method \_SB.PCI0.RP13.XGBE._PSW due to previous error (AE_TIME) (20230628/psparse-529)
Sep 07 07:12:35 user kernel: ACPI Error: AE_TIME, Returned by Handler for [EmbeddedControl] (20230628/evregion-300)
Sep 07 07:12:35 user kernel: ACPI Error: Timeout from EC hardware or EC device driver (20230628/evregion-310)
Sep 07 07:12:35 user kernel: ACPI Error: Aborting method \_SB.PC04.MCP0.US00.DS09.UPSB.DSB2.XHC4._PSW due to previous error (AE_TIME) (20230628/psparse-529)
Sep 07 07:12:35 user kernel: ACPI Error: AE_TIME, Returned by Handler for [EmbeddedControl] (20230628/evregion-300)
Sep 07 07:12:35 user kernel: ACPI Error: Timeout from EC hardware or EC device driver (20230628/evregion-310)
Sep 07 07:12:35 user kernel: ACPI Error: Aborting method \_SB.PC04.MCP0.US00.DS0A.UPSB.DSB2.XHC5._PSW due to previous error (AE_TIME) (20230628/psparse-529)
Sep 07 07:12:35 user kernel: ACPI Error: AE_TIME, Returned by Handler for [EmbeddedControl] (20230628/evregion-300)
Sep 07 07:12:35 user kernel: ACPI Error: Timeout from EC hardware or EC device driver (20230628/evregion-310)
Sep 07 07:12:35 user kernel: ACPI Error: Aborting method \_SB.PC04.MCP0.US00.DS18.UPSB.DSB2.XHC2._PSW due to previous error (AE_TIME) (20230628/psparse-529)
Sep 07 07:12:35 user kernel: ACPI Error: AE_TIME, Returned by Handler for [EmbeddedControl] (20230628/evregion-300)
Sep 07 07:12:35 user kernel: ACPI Error: Timeout from EC hardware or EC device driver (20230628/evregion-310)
Sep 07 07:12:35 user kernel: ACPI Error: Aborting method \_SB.PC04.MCP0.US00.DS19.UPSB.DSB2.XHC3._PSW due to previous error (AE_TIME) (20230628/psparse-529)
Sep 07 07:12:35 user kernel: ACPI Error: AE_TIME, Returned by Handler for [EmbeddedControl] (20230628/evregion-300)
Sep 07 07:12:35 user kernel: ACPI Error: Timeout from EC hardware or EC device driver (20230628/evregion-310)
Sep 07 07:12:35 user kernel: ACPI Error: Aborting method \_SB.PC04.MCP0.US00.DS1A.UPSB.DSB2.XHC6._PSW due to previous error (AE_TIME) (20230628/psparse-529)
Sep 07 07:12:35 user kernel: ACPI Error: AE_TIME, Returned by Handler for [EmbeddedControl] (20230628/evregion-300)
Sep 07 07:12:35 user kernel: ACPI Error: Timeout from EC hardware or EC device driver (20230628/evregion-310)
Sep 07 07:12:35 user kernel: ACPI Error: Aborting method \_SB.PC04.MCP0.US00.DS1B.UPSB.DSB2.XHC7._PSW due to previous error (AE_TIME) (20230628/psparse-529)
Sep 07 07:12:35 user kernel: ACPI Error: AE_TIME, Returned by Handler for [EmbeddedControl] (20230628/evregion-300)
Sep 07 07:12:35 user kernel: ACPI Error: Timeout from EC hardware or EC device driver (20230628/evregion-310)
Sep 07 07:12:35 user kernel: ACPI Error: Aborting method \_SB.PCI0.LPCB.EC._REG due to previous error (AE_TIME) (20230628/psparse-529)
Sep 07 07:12:35 user kernel: apple-properties: device path parse error -19 at 0x32:
Sep 07 07:12:35 user kernel: apple-properties: 00000000: 10 01 00 00 03 00 00 00 02 01 0c 00 d0 41 03 0a  .............A..
Sep 07 07:12:35 user kernel: apple-properties: 00000010: 04 00 00 00 01 01 06 00 00 00 01 01 06 00 00 00  ................
Sep 07 07:12:35 user kernel: apple-properties: 00000020: 01 01 06 00 00 09 01 01 06 00 00 00 01 01 06 00  ................
Sep 07 07:12:35 user kernel: apple-properties: 00000030: 00 01 01 01 06 00 00 00 7f ff 04 00 46 00 00 00  ............F...
Sep 07 07:12:35 user kernel: apple-properties: 00000040: 54 00 75 00 6e 00 6e 00 65 00 6c 00 20 00 45 00  T.u.n.n.e.l. .E.
Sep 07 07:12:35 user kernel: apple-properties: 00000050: 6e 00 64 00 70 00 6f 00 69 00 6e 00 74 00 20 00  n.d.p.o.i.n.t. .
Sep 07 07:12:35 user kernel: apple-properties: 00000060: 44 00 65 00 76 00 69 00 63 00 65 00 20 00 56 00  D.e.v.i.c.e. .V.
Sep 07 07:12:35 user kernel: apple-properties: 00000070: 65 00 6e 00 64 00 6f 00 72 00 20 00 49 00 44 00  e.n.d.o.r. .I.D.
Sep 07 07:12:35 user kernel: apple-properties: 00000080: 00 00 08 00 00 00 5a 00 00 00 44 00 00 00 54 00  ......Z...D...T.
Sep 07 07:12:35 user kernel: apple-properties: 00000090: 75 00 6e 00 6e 00 65 00 6c 00 20 00 45 00 6e 00  u.n.n.e.l. .E.n.
Sep 07 07:12:35 user kernel: apple-properties: 000000a0: 64 00 70 00 6f 00 69 00 6e 00 74 00 20 00 44 00  d.p.o.i.n.t. .D.
Sep 07 07:12:35 user kernel: apple-properties: 000000b0: 65 00 76 00 69 00 63 00 65 00 20 00 4d 00 6f 00  e.v.i.c.e. .M.o.
Sep 07 07:12:35 user kernel: apple-properties: 000000c0: 64 00 65 00 6c 00 20 00 49 00 44 00 00 00 08 00  d.e.l. .I.D.....
Sep 07 07:12:35 user kernel: apple-properties: 000000d0: 00 00 21 de 00 00 2e 00 00 00 54 00 75 00 6e 00  ..!.......T.u.n.
Sep 07 07:12:35 user kernel: apple-properties: 000000e0: 6e 00 65 00 6c 00 20 00 45 00 6e 00 64 00 70 00  n.e.l. .E.n.d.p.
Sep 07 07:12:35 user kernel: apple-properties: 000000f0: 6f 00 69 00 6e 00 74 00 20 00 47 00 55 00 49 00  o.i.n.t. .G.U.I.
Sep 07 07:12:35 user kernel: apple-properties: 00000100: 44 00 00 00 0c 00 00 00 00 c3 f9 68 dc cf 5a 00  D..........h..Z.
Sep 07 07:12:35 user kernel: apple-properties: device path parse error -19 at 0x32:
Sep 07 07:12:35 user kernel: apple-properties: 00000000: 10 01 00 00 03 00 00 00 02 01 0c 00 d0 41 03 0a  .............A..
Sep 07 07:12:35 user kernel: apple-properties: 00000010: 04 00 00 00 01 01 06 00 00 00 01 01 06 00 00 00  ................
Sep 07 07:12:35 user kernel: apple-properties: 00000020: 01 01 06 00 00 0a 01 01 06 00 00 00 01 01 06 00  ................
Sep 07 07:12:35 user kernel: apple-properties: 00000030: 00 04 01 01 06 00 00 00 7f ff 04 00 46 00 00 00  ............F...
Sep 07 07:12:35 user kernel: apple-properties: 00000040: 54 00 75 00 6e 00 6e 00 65 00 6c 00 20 00 45 00  T.u.n.n.e.l. .E.
Sep 07 07:12:35 user kernel: apple-properties: 00000050: 6e 00 64 00 70 00 6f 00 69 00 6e 00 74 00 20 00  n.d.p.o.i.n.t. .
Sep 07 07:12:35 user kernel: apple-properties: 00000060: 44 00 65 00 76 00 69 00 63 00 65 00 20 00 56 00  D.e.v.i.c.e. .V.
Sep 07 07:12:35 user kernel: apple-properties: 00000070: 65 00 6e 00 64 00 6f 00 72 00 20 00 49 00 44 00  e.n.d.o.r. .I.D.
Sep 07 07:12:35 user kernel: apple-properties: 00000080: 00 00 08 00 00 00 01 00 00 00 44 00 00 00 54 00  ..........D...T.
Sep 07 07:12:35 user kernel: apple-properties: 00000090: 75 00 6e 00 6e 00 65 00 6c 00 20 00 45 00 6e 00  u.n.n.e.l. .E.n.
Sep 07 07:12:35 user kernel: apple-properties: 000000a0: 64 00 70 00 6f 00 69 00 6e 00 74 00 20 00 44 00  d.p.o.i.n.t. .D.
Sep 07 07:12:35 user kernel: apple-properties: 000000b0: 65 00 76 00 69 00 63 00 65 00 20 00 4d 00 6f 00  e.v.i.c.e. .M.o.
Sep 07 07:12:35 user kernel: apple-properties: 000000c0: 64 00 65 00 6c 00 20 00 49 00 44 00 00 00 08 00  d.e.l. .I.D.....
Sep 07 07:12:35 user kernel: apple-properties: 000000d0: 00 00 02 80 00 00 2e 00 00 00 54 00 75 00 6e 00  ..........T.u.n.
Sep 07 07:12:35 user kernel: apple-properties: 000000e0: 6e 00 65 00 6c 00 20 00 45 00 6e 00 64 00 70 00  n.e.l. .E.n.d.p.
Sep 07 07:12:35 user kernel: apple-properties: 000000f0: 6f 00 69 00 6e 00 74 00 20 00 47 00 55 00 49 00  o.i.n.t. .G.U.I.
Sep 07 07:12:35 user kernel: apple-properties: 00000100: 44 00 00 00 0c 00 00 00 e0 f4 9a 00 01 00 01 00  D...............
Sep 07 07:12:35 user kernel: integrity: Reading UEFI Secure Boot Certs is not supported on T2 Macs.
Sep 07 07:12:35 user kernel: spi-nor spi0.0: unrecognized JEDEC id bytes: f4 00 9c 36 03 00
Sep 07 07:12:35 user kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4364b3-pcie for chip BCM4364/4
Sep 07 07:12:38 user kernel: brcmfmac: brcmf_c_process_txcap_blob: TxCap blob found, loading
Sep 07 07:12:38 user kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4364/4 wl0: Dec  9 2022 17:02:25 version 9.30.492.0.32.5.87 FWID 01-e7856862
Sep 07 07:12:41 user gdm-autologin][2702]: gkr-pam: couldn't unlock the login keyring.
Sep 07 07:12:41 user systemd[2712]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-2862.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 226 and the job result is failed.
Sep 07 07:12:41 user systemd[2712]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-2859.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 222 and the job result is failed.
Sep 07 07:12:41 user systemd[2712]: Failed to start app-gnome-xdg\x2duser\x2ddirs-2879.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 238 and the job result is failed.
Sep 07 07:12:42 user systemd[2712]: Failed to start app-gnome-user\x2ddirs\x2dupdate\x2dgtk-3136.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 340 and the job result is failed.
Sep 07 07:12:44 user kernel: usb 15-1.4: 1:1: cannot get freq at ep 0x4
Sep 07 07:12:45 user kernel: usb 15-1.4: 1:2: cannot get freq at ep 0x4
Sep 07 07:12:45 user kernel: usb 15-1.4: 2:1: cannot get freq at ep 0x84
Sep 07 07:12:45 user kernel: pcieport 0000:8a:02.0: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Requester ID)
Sep 07 07:12:45 user kernel: pcieport 0000:8a:02.0:   device [8086:15ea] error status/mask=00300000/00000000
Sep 07 07:12:45 user kernel: pcieport 0000:8a:02.0:    [20] UnsupReq               (First)
Sep 07 07:12:45 user kernel: pcieport 0000:8a:02.0:    [21] ACSViol               
Sep 07 07:12:45 user kernel: pcieport 0000:8a:02.0: AER:   TLP Header: 34000000 00000010 00000000 00000000

Adding kernel parameters:
GRUB_CMDLINE_LINUX="quiet splash" intel_iommu=on iommu=pt pcie_ports=compat
adding CONFIG_MODULE_FORCE_UNLOAD=y in addition caused the graphics to not come back up after unplugging and plugging in the thunderbolt display, so removed all the kernel parameters again.

journalctl -p 3 -xb
Sep 07 08:30:26 amiga kernel: ACPI Error: AE_TIME, Returned by Handler for [EmbeddedControl] (20230628/evregion-300)
Sep 07 08:30:26 amiga kernel: ACPI Error: Timeout from EC hardware or EC device driver (20230628/evregion-310)
Sep 07 08:30:26 amiga kernel: ACPI Error: Aborting method \_SB.PCI0.RP01.ARPT._PSW due to previous error (AE_TIME) (20230628/psparse-529)
Sep 07 08:30:26 amiga kernel: ACPI Error: AE_TIME, Returned by Handler for [EmbeddedControl] (20230628/evregion-300)
Sep 07 08:30:26 amiga kernel: ACPI Error: Timeout from EC hardware or EC device driver (20230628/evregion-310)
Sep 07 08:30:26 amiga kernel: ACPI Error: Aborting method \_SB.PCI0.RP09.XGBE._PSW due to previous error (AE_TIME) (20230628/psparse-529)
Sep 07 08:30:26 amiga kernel: ACPI Error: AE_TIME, Returned by Handler for [EmbeddedControl] (20230628/evregion-300)
Sep 07 08:30:26 amiga kernel: ACPI Error: Timeout from EC hardware or EC device driver (20230628/evregion-310)
Sep 07 08:30:26 amiga kernel: ACPI Error: Aborting method \_SB.PCI0.RP13.XGBE._PSW due to previous error (AE_TIME) (20230628/psparse-529)
Sep 07 08:30:26 amiga kernel: ACPI Error: AE_TIME, Returned by Handler for [EmbeddedControl] (20230628/evregion-300)
Sep 07 08:30:26 amiga kernel: ACPI Error: Timeout from EC hardware or EC device driver (20230628/evregion-310)
Sep 07 08:30:26 amiga kernel: ACPI Error: Aborting method \_SB.PC04.MCP0.US00.DS09.UPSB.DSB2.XHC4._PSW due to previous error (AE_TIME) (20230628/pspars>
Sep 07 08:30:26 amiga kernel: ACPI Error: AE_TIME, Returned by Handler for [EmbeddedControl] (20230628/evregion-300)
Sep 07 08:30:26 amiga kernel: ACPI Error: Timeout from EC hardware or EC device driver (20230628/evregion-310)
Sep 07 08:30:26 amiga kernel: ACPI Error: Aborting method \_SB.PC04.MCP0.US00.DS0A.UPSB.DSB2.XHC5._PSW due to previous error (AE_TIME) (20230628/pspars>
Sep 07 08:30:26 amiga kernel: ACPI Error: AE_TIME, Returned by Handler for [EmbeddedControl] (20230628/evregion-300)
Sep 07 08:30:26 amiga kernel: ACPI Error: Timeout from EC hardware or EC device driver (20230628/evregion-310)
Sep 07 08:30:26 amiga kernel: ACPI Error: Aborting method \_SB.PC04.MCP0.US00.DS18.UPSB.DSB2.XHC2._PSW due to previous error (AE_TIME) (20230628/pspars>
Sep 07 08:30:26 amiga kernel: ACPI Error: AE_TIME, Returned by Handler for [EmbeddedControl] (20230628/evregion-300)
Sep 07 08:30:26 amiga kernel: ACPI Error: Timeout from EC hardware or EC device driver (20230628/evregion-310)
Sep 07 08:30:26 amiga kernel: ACPI Error: Aborting method \_SB.PC04.MCP0.US00.DS19.UPSB.DSB2.XHC3._PSW due to previous error (AE_TIME) (20230628/pspars>
Sep 07 08:30:26 amiga kernel: ACPI Error: AE_TIME, Returned by Handler for [EmbeddedControl] (20230628/evregion-300)
Sep 07 08:30:26 amiga kernel: ACPI Error: Timeout from EC hardware or EC device driver (20230628/evregion-310)
Sep 07 08:30:26 amiga kernel: ACPI Error: Aborting method \_SB.PC04.MCP0.US00.DS1A.UPSB.DSB2.XHC6._PSW due to previous error (AE_TIME) (20230628/pspars>
Sep 07 08:30:26 amiga kernel: ACPI Error: AE_TIME, Returned by Handler for [EmbeddedControl] (20230628/evregion-300)
Sep 07 08:30:26 amiga kernel: ACPI Error: Timeout from EC hardware or EC device driver (20230628/evregion-310)
Sep 07 08:30:26 amiga kernel: ACPI Error: Aborting method \_SB.PC04.MCP0.US00.DS1B.UPSB.DSB2.XHC7._PSW due to previous error (AE_TIME) (20230628/pspars>
Sep 07 08:30:26 amiga kernel: ACPI Error: AE_TIME, Returned by Handler for [EmbeddedControl] (20230628/evregion-300)
Sep 07 08:30:26 amiga kernel: ACPI Error: Timeout from EC hardware or EC device driver (20230628/evregion-310)
Sep 07 08:30:26 amiga kernel: ACPI Error: Aborting method \_SB.PCI0.LPCB.EC._REG due to previous error (AE_TIME) (20230628/psparse-529)
Sep 07 08:30:26 amiga kernel: apple-properties: device path parse error -19 at 0x32:
Sep 07 08:30:26 amiga kernel: apple-properties: 00000000: 10 01 00 00 03 00 00 00 02 01 0c 00 d0 41 03 0a  .............A..
Sep 07 08:30:26 amiga kernel: apple-properties: 00000010: 04 00 00 00 01 01 06 00 00 00 01 01 06 00 00 00  ................
Sep 07 08:30:26 amiga kernel: apple-properties: 00000020: 01 01 06 00 00 09 01 01 06 00 00 00 01 01 06 00  ................
Sep 07 08:30:26 amiga kernel: apple-properties: 00000030: 00 01 01 01 06 00 00 00 7f ff 04 00 46 00 00 00  ............F...
Sep 07 08:30:26 amiga kernel: apple-properties: 00000040: 54 00 75 00 6e 00 6e 00 65 00 6c 00 20 00 45 00  T.u.n.n.e.l. .E.
Sep 07 08:30:26 amiga kernel: apple-properties: 00000050: 6e 00 64 00 70 00 6f 00 69 00 6e 00 74 00 20 00  n.d.p.o.i.n.t. .
Sep 07 08:30:26 amiga kernel: apple-properties: 00000060: 44 00 65 00 76 00 69 00 63 00 65 00 20 00 56 00  D.e.v.i.c.e. .V.
Sep 07 08:30:26 amiga kernel: apple-properties: 00000070: 65 00 6e 00 64 00 6f 00 72 00 20 00 49 00 44 00  e.n.d.o.r. .I.D.
Sep 07 08:30:26 amiga kernel: apple-properties: 00000080: 00 00 08 00 00 00 5a 00 00 00 44 00 00 00 54 00  ......Z...D...T.
Sep 07 08:30:26 amiga kernel: apple-properties: 00000090: 75 00 6e 00 6e 00 65 00 6c 00 20 00 45 00 6e 00  u.n.n.e.l. .E.n.
Sep 07 08:30:26 amiga kernel: apple-properties: 000000a0: 64 00 70 00 6f 00 69 00 6e 00 74 00 20 00 44 00  d.p.o.i.n.t. .D.
Sep 07 08:30:26 amiga kernel: apple-properties: 000000b0: 65 00 76 00 69 00 63 00 65 00 20 00 4d 00 6f 00  e.v.i.c.e. .M.o.
Sep 07 08:30:26 amiga kernel: apple-properties: 000000c0: 64 00 65 00 6c 00 20 00 49 00 44 00 00 00 08 00  d.e.l. .I.D.....
Sep 07 08:30:26 amiga kernel: apple-properties: 000000d0: 00 00 21 de 00 00 2e 00 00 00 54 00 75 00 6e 00  ..!.......T.u.n.
Sep 07 08:30:26 amiga kernel: apple-properties: 000000e0: 6e 00 65 00 6c 00 20 00 45 00 6e 00 64 00 70 00  n.e.l. .E.n.d.p.
Sep 07 08:30:26 amiga kernel: apple-properties: 000000f0: 6f 00 69 00 6e 00 74 00 20 00 47 00 55 00 49 00  o.i.n.t. .G.U.I.
Sep 07 08:30:26 amiga kernel: apple-properties: 00000100: 44 00 00 00 0c 00 00 00 00 c3 f9 68 dc cf 5a 00  D..........h..Z.
Sep 07 08:30:26 amiga kernel: apple-properties: device path parse error -19 at 0x32:
Sep 07 08:30:26 amiga kernel: apple-properties: 00000000: 10 01 00 00 03 00 00 00 02 01 0c 00 d0 41 03 0a  .............A..
Sep 07 08:30:26 amiga kernel: apple-properties: 00000010: 04 00 00 00 01 01 06 00 00 00 01 01 06 00 00 00  ................
Sep 07 08:30:26 amiga kernel: apple-properties: 00000020: 01 01 06 00 00 0a 01 01 06 00 00 00 01 01 06 00  ................
Sep 07 08:30:26 amiga kernel: apple-properties: 00000030: 00 01 01 01 06 00 00 00 7f ff 04 00 46 00 00 00  ............F...
Sep 07 08:30:26 amiga kernel: apple-properties: 00000040: 54 00 75 00 6e 00 6e 00 65 00 6c 00 20 00 45 00  T.u.n.n.e.l. .E.
Sep 07 08:30:26 amiga kernel: apple-properties: 00000050: 6e 00 64 00 70 00 6f 00 69 00 6e 00 74 00 20 00  n.d.p.o.i.n.t. .
Sep 07 08:30:26 amiga kernel: apple-properties: 00000060: 44 00 65 00 76 00 69 00 63 00 65 00 20 00 56 00  D.e.v.i.c.e. .V.
Sep 07 08:30:26 amiga kernel: apple-properties: 00000070: 65 00 6e 00 64 00 6f 00 72 00 20 00 49 00 44 00  e.n.d.o.r. .I.D.
Sep 07 08:30:26 amiga kernel: apple-properties: 00000080: 00 00 08 00 00 00 03 00 00 00 44 00 00 00 54 00  ..........D...T.
Sep 07 08:30:26 amiga kernel: apple-properties: 00000090: 75 00 6e 00 6e 00 65 00 6c 00 20 00 45 00 6e 00  u.n.n.e.l. .E.n.
Sep 07 08:30:26 amiga kernel: apple-properties: 000000a0: 64 00 70 00 6f 00 69 00 6e 00 74 00 20 00 44 00  d.p.o.i.n.t. .D.
Sep 07 08:30:26 amiga kernel: apple-properties: 000000b0: 65 00 76 00 69 00 63 00 65 00 20 00 4d 00 6f 00  e.v.i.c.e. .M.o.
Sep 07 08:30:26 amiga kernel: apple-properties: 000000c0: 64 00 65 00 6c 00 20 00 49 00 44 00 00 00 08 00  d.e.l. .I.D.....
Sep 07 08:30:26 amiga kernel: apple-properties: 000000d0: 00 00 02 00 00 00 2e 00 00 00 54 00 75 00 6e 00  ..........T.u.n.
Sep 07 08:30:26 amiga kernel: apple-properties: 000000e0: 6e 00 65 00 6c 00 20 00 45 00 6e 00 64 00 70 00  n.e.l. .E.n.d.p.
Sep 07 08:30:26 amiga kernel: apple-properties: 000000f0: 6f 00 69 00 6e 00 74 00 20 00 47 00 55 00 49 00  o.i.n.t. .G.U.I.
Sep 07 08:30:26 amiga kernel: apple-properties: 00000100: 44 00 00 00 0c 00 00 00 10 ed d4 0f 00 00 03 00  D...............
Sep 07 08:30:26 amiga kernel: apple-properties: device path parse error -19 at 0x32:
Sep 07 08:30:26 amiga kernel: apple-properties: 00000000: 10 01 00 00 03 00 00 00 02 01 0c 00 d0 41 03 0a  .............A..
Sep 07 08:30:26 amiga kernel: apple-properties: 00000010: 04 00 00 00 01 01 06 00 00 00 01 01 06 00 00 00  ................
Sep 07 08:30:26 amiga kernel: apple-properties: 00000020: 01 01 06 00 00 0a 01 01 06 00 00 00 01 01 06 00  ................
Sep 07 08:30:26 amiga kernel: apple-properties: 00000030: 00 04 01 01 06 00 00 00 7f ff 04 00 46 00 00 00  ............F...
Sep 07 08:30:26 amiga kernel: apple-properties: 00000040: 54 00 75 00 6e 00 6e 00 65 00 6c 00 20 00 45 00  T.u.n.n.e.l. .E.
Sep 07 08:30:26 amiga kernel: apple-properties: 00000050: 6e 00 64 00 70 00 6f 00 69 00 6e 00 74 00 20 00  n.d.p.o.i.n.t. .
Sep 07 08:30:26 amiga kernel: apple-properties: 00000060: 44 00 65 00 76 00 69 00 63 00 65 00 20 00 56 00  D.e.v.i.c.e. .V.
Sep 07 08:30:26 amiga kernel: apple-properties: 00000070: 65 00 6e 00 64 00 6f 00 72 00 20 00 49 00 44 00  e.n.d.o.r. .I.D.
Sep 07 08:30:26 amiga kernel: apple-properties: 00000080: 00 00 08 00 00 00 01 00 00 00 44 00 00 00 54 00  ..........D...T.
Sep 07 08:30:26 amiga kernel: apple-properties: 00000090: 75 00 6e 00 6e 00 65 00 6c 00 20 00 45 00 6e 00  u.n.n.e.l. .E.n.
Sep 07 08:30:26 amiga kernel: apple-properties: 000000a0: 64 00 70 00 6f 00 69 00 6e 00 74 00 20 00 44 00  d.p.o.i.n.t. .D.
Sep 07 08:30:26 amiga kernel: apple-properties: 000000b0: 65 00 76 00 69 00 63 00 65 00 20 00 4d 00 6f 00  e.v.i.c.e. .M.o.
Sep 07 08:30:26 amiga kernel: apple-properties: 000000c0: 64 00 65 00 6c 00 20 00 49 00 44 00 00 00 08 00  d.e.l. .I.D.....
Sep 07 08:30:26 amiga kernel: apple-properties: 000000d0: 00 00 02 80 00 00 2e 00 00 00 54 00 75 00 6e 00  ..........T.u.n.
Sep 07 08:30:26 amiga kernel: apple-properties: 000000e0: 6e 00 65 00 6c 00 20 00 45 00 6e 00 64 00 70 00  n.e.l. .E.n.d.p.
Sep 07 08:30:26 amiga kernel: apple-properties: 000000f0: 6f 00 69 00 6e 00 74 00 20 00 47 00 55 00 49 00  o.i.n.t. .G.U.I.
Sep 07 08:30:26 amiga kernel: apple-properties: 00000100: 44 00 00 00 0c 00 00 00 e0 f4 9a 00 01 00 01 00  D...............
Sep 07 08:30:26 amiga kernel: integrity: Reading UEFI Secure Boot Certs is not supported on T2 Macs.
Sep 07 08:30:26 amiga kernel: spi-nor spi0.0: unrecognized JEDEC id bytes: f4 00 9c 36 03 00
Sep 07 08:30:26 amiga kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4364b3-pcie for chip BCM4364/4
Sep 07 08:30:29 amiga kernel: brcmfmac: brcmf_c_process_txcap_blob: TxCap blob found, loading
Sep 07 08:30:29 amiga kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4364/4 wl0: Dec  9 2022 17:02:25 version 9.30.492.0.32.5.87 FWID 01-e7856862
Sep 07 08:30:32 amiga gdm-autologin][2479]: gkr-pam: couldn't unlock the login keyring.
Sep 07 08:30:32 amiga systemd[2538]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-2853.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 222 and the job result is failed.
Sep 07 08:30:32 amiga systemd[2538]: Failed to start app-gnome-xdg\x2duser\x2ddirs-2872.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 234 and the job result is failed.
Sep 07 08:30:33 amiga systemd[2538]: Failed to start app-gnome-user\x2ddirs\x2dupdate\x2dgtk-3163.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 336 and the job result is failed.
Sep 07 08:30:35 amiga kernel: usb 15-1.4: 1:1: cannot get freq at ep 0x4
Sep 07 08:30:36 amiga kernel: usb 15-1.4: 1:2: cannot get freq at ep 0x4
Sep 07 08:30:36 amiga kernel: usb 15-1.4: 2:1: cannot get freq at ep 0x84
Sep 07 08:30:37 amiga kernel: pcieport 0000:8a:02.0: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Requester ID)
Sep 07 08:30:37 amiga kernel: pcieport 0000:8a:02.0:   device [8086:15ea] error status/mask=00300000/00000000
Sep 07 08:30:37 amiga kernel: pcieport 0000:8a:02.0:    [20] UnsupReq               (First)
Sep 07 08:30:37 amiga kernel: pcieport 0000:8a:02.0:    [21] ACSViol               
Sep 07 08:30:37 amiga kernel: pcieport 0000:8a:02.0: AER:   TLP Header: 34000000 00000010 00000000 00000000
Sep 07 08:29:55 amiga nm-openvpn[3685]: event_wait : Interrupted system call (fd=-1,code=4)
Sep 07 08:31:30 amiga kernel: pcieport 0000:8a:02.0: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Requester ID)
Sep 07 08:31:30 amiga kernel: pcieport 0000:8a:02.0:   device [8086:15ea] error status/mask=00300000/00000000
Sep 07 08:31:30 amiga kernel: pcieport 0000:8a:02.0:    [20] UnsupReq               (First)
Sep 07 08:31:30 amiga kernel: pcieport 0000:8a:02.0:    [21] ACSViol               
Sep 07 08:31:30 amiga kernel: pcieport 0000:8a:02.0: AER:   TLP Header: 34000000 00000010 00000000 00000000
Sep 07 08:31:30 amiga kernel: ACPI Error: AE_TIME, Returned by Handler for [EmbeddedControl] (20230628/evregion-300)
Sep 07 08:31:30 amiga kernel: ACPI Error: Timeout from EC hardware or EC device driver (20230628/evregion-310)
Sep 07 08:31:30 amiga kernel: ACPI Error: Aborting method \_SB.PCI0.RP17._PS3 due to previous error (AE_TIME) (20230628/psparse-529)
Sep 07 08:31:30 amiga kernel: ACPI Error: AE_TIME, Returned by Handler for [EmbeddedControl] (20230628/evregion-300)
Sep 07 08:31:30 amiga kernel: ACPI Error: Timeout from EC hardware or EC device driver (20230628/evregion-310)
Sep 07 08:31:30 amiga kernel: ACPI Error: Aborting method \_PTS due to previous error (AE_TIME) (20230628/psparse-529)
Sep 07 08:31:30 amiga kernel: ACPI Error: AE_TIME, Returned by Handler for [EmbeddedControl] (20230628/evregion-300)
Sep 07 08:31:30 amiga kernel: ACPI Error: Timeout from EC hardware or EC device driver (20230628/evregion-310)
Sep 07 08:31:30 amiga kernel: ACPI Error: Aborting method \_WAK due to previous error (AE_TIME) (20230628/psparse-529)
Sep 07 08:31:30 amiga kernel: ACPI Error: AE_TIME, While executing method \_WAK (20230628/hwesleep-47)
Sep 07 08:31:30 amiga kernel: ACPI Error: Aborting method \_SB.PC04.MCP0.US00.DS0A.UPSB.PCED due to previous error (AE_AML_LOOP_TIMEOUT) (20230628/pspa>
Sep 07 08:31:30 amiga kernel: ACPI Error: Aborting method \_SB.PC04.MCP0.US00.DS0A.UPSB._PS0 due to previous error (AE_AML_LOOP_TIMEOUT) (20230628/pspa>
Sep 07 08:31:30 amiga kernel: pcieport 0000:8d:00.0: Unable to change power state from D3hot to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: pcieport 0000:92:00.0: Unable to change power state from D3hot to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: pcieport 0000:8e:04.0: Unable to change power state from D3hot to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: pcieport 0000:8e:05.0: Unable to change power state from D3hot to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: pcieport 0000:93:00.0: Unable to change power state from D3hot to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: pcieport 0000:93:02.0: Unable to change power state from D3hot to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: pcieport 0000:93:01.0: Unable to change power state from D3hot to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: pcieport 0000:93:05.0: Unable to change power state from D3hot to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: pcieport 0000:93:04.0: Unable to change power state from D3hot to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: pcieport 0000:8e:03.0: Unable to change power state from D3hot to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: ACPI Error: Aborting method \_SB.PC04.MCP0.US00.DS09.UPSB.PCED due to previous error (AE_AML_LOOP_TIMEOUT) (20230628/pspa>
Sep 07 08:31:30 amiga kernel: ACPI Error: Aborting method \_SB.PC04.MCP0.US00.DS09.UPSB._PS0 due to previous error (AE_AML_LOOP_TIMEOUT) (20230628/pspa>
Sep 07 08:31:30 amiga kernel: firewire_ohci 0000:98:00.0: Unable to change power state from D3hot to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: pcieport 0000:20:00.0: Unable to change power state from D3hot to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: pcieport 0000:94:00.0: Unable to change power state from D3hot to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: tg3 0000:97:00.0: Unable to change power state from D3hot to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: ahci 0000:8f:00.0: Unable to change power state from D3hot to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: pcieport 0000:21:01.0: Unable to change power state from D3hot to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: pcieport 0000:21:03.0: Unable to change power state from D3hot to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: pcieport 0000:95:03.0: Unable to change power state from D3hot to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: pcieport 0000:21:04.0: Unable to change power state from D3hot to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: pcieport 0000:21:00.0: Unable to change power state from D3hot to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: pcieport 0000:21:02.0: Unable to change power state from D3hot to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: ohci-pci 0000:96:00.0: Unable to change power state from D3hot to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: ehci-pci 0000:96:00.2: Unable to change power state from D3hot to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: ohci-pci 0000:96:00.1: Unable to change power state from D3hot to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: xhci_hcd 0000:23:00.0: Unable to change power state from D3hot to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: igb 0000:25:00.0: Unable to change power state from D3hot to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: xhci_hcd 0000:22:00.0: Unable to change power state from D3hot to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: xhci_hcd 0000:24:00.0: Unable to change power state from D3hot to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: xhci_hcd 0000:24:00.0: Unable to change power state from D3cold to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: xhci_hcd 0000:23:00.0: Unable to change power state from D3cold to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: igb 0000:25:00.0: Unable to change power state from D3cold to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: xhci_hcd 0000:22:00.0: Unable to change power state from D3cold to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: xhci_hcd 0000:24:00.0: PCI post-resume error -19!
Sep 07 08:31:30 amiga kernel: xhci_hcd 0000:24:00.0: HC died; cleaning up
Sep 07 08:31:30 amiga kernel: xhci_hcd 0000:23:00.0: PCI post-resume error -19!
Sep 07 08:31:30 amiga kernel: xhci_hcd 0000:23:00.0: HC died; cleaning up
Sep 07 08:31:30 amiga kernel: xhci_hcd 0000:22:00.0: PCI post-resume error -19!
Sep 07 08:31:30 amiga kernel: igb 0000:25:00.0: PM: dpm_run_callback(): pci_pm_resume+0x0/0x110 returns -19
Sep 07 08:31:30 amiga kernel: xhci_hcd 0000:22:00.0: HC died; cleaning up
Sep 07 08:31:30 amiga kernel: igb 0000:25:00.0: PM: failed to resume async: error -19
Sep 07 08:31:30 amiga kernel: xhci_hcd 0000:24:00.0: PM: dpm_run_callback(): pci_pm_resume+0x0/0x110 returns -19
Sep 07 08:31:30 amiga kernel: xhci_hcd 0000:23:00.0: PM: dpm_run_callback(): pci_pm_resume+0x0/0x110 returns -19
Sep 07 08:31:30 amiga kernel: xhci_hcd 0000:24:00.0: PM: failed to resume async: error -19
Sep 07 08:31:30 amiga kernel: xhci_hcd 0000:22:00.0: PM: dpm_run_callback(): pci_pm_resume+0x0/0x110 returns -19
Sep 07 08:31:30 amiga kernel: xhci_hcd 0000:23:00.0: PM: failed to resume async: error -19
Sep 07 08:31:30 amiga kernel: xhci_hcd 0000:22:00.0: PM: failed to resume async: error -19
Sep 07 08:31:30 amiga kernel: ohci-pci 0000:96:00.0: Unable to change power state from D3cold to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: ohci-pci 0000:96:00.1: Unable to change power state from D3cold to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: ehci-pci 0000:96:00.2: Unable to change power state from D3cold to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: usb 1-3: device descriptor read/64, error -71
Sep 07 08:31:30 amiga kernel: usb 1-3: device descriptor read/64, error -71
Sep 07 08:31:30 amiga kernel: ahci 0000:8f:00.0: Controller reset failed (0xffffffff)
Sep 07 08:31:30 amiga kernel: ahci 0000:8f:00.0: PM: dpm_run_callback(): pci_pm_resume+0x0/0x110 returns -5
Sep 07 08:31:30 amiga kernel: ahci 0000:8f:00.0: PM: failed to resume async: error -5
Sep 07 08:31:30 amiga kernel: ahci 0000:8f:00.0: AHCI controller unavailable!
Sep 07 08:31:30 amiga kernel: ahci 0000:8f:00.0: AHCI controller unavailable!
Sep 07 08:31:30 amiga kernel: ahci 0000:8f:00.0: AHCI controller unavailable!
Sep 07 08:31:30 amiga kernel: ahci 0000:8f:00.0: AHCI controller unavailable!
Sep 07 08:31:30 amiga kernel: usb 1-3: device descriptor read/64, error -71
Sep 07 08:31:30 amiga kernel: usb 1-3: device descriptor read/64, error -71
Sep 07 08:31:30 amiga kernel: usb 1-3: device not accepting address 2, error -71
Sep 07 08:31:30 amiga kernel: usb 1-3: device not accepting address 2, error -71
Sep 07 08:31:30 amiga kernel: xpad 11-2:1.0: xpad_try_sending_next_out_packet - usb_submit_urb failed with result -19
Sep 07 08:31:30 amiga kernel: ohci-pci 0000:96:00.0: USB HC takeover failed!  (BIOS/SMM bug)
Sep 07 08:31:30 amiga kernel: ohci-pci 0000:96:00.1: USB HC takeover failed!  (BIOS/SMM bug)
Sep 07 08:31:30 amiga kernel: ohci-pci 0000:96:00.0: USB HC reset timed out!
Sep 07 08:31:30 amiga kernel: ohci-pci 0000:96:00.0: can't restart, -1
Sep 07 08:31:30 amiga kernel: ohci-pci 0000:96:00.1: USB HC reset timed out!
Sep 07 08:31:30 amiga kernel: ohci-pci 0000:96:00.1: can't restart, -1
Sep 07 08:31:30 amiga kernel: ehci-pci 0000:96:00.2: HC died; cleaning up
Sep 07 08:31:30 amiga kernel: ohci-pci 0000:96:00.1: HC died; cleaning up
Sep 07 08:31:30 amiga kernel: ahci 0000:8f:00.0: AHCI controller unavailable!
Sep 07 08:31:30 amiga kernel: ohci-pci 0000:96:00.0: USB HC takeover failed!  (BIOS/SMM bug)
Sep 07 08:31:30 amiga kernel: ohci-pci 0000:96:00.1: USB HC takeover failed!  (BIOS/SMM bug)
Sep 07 08:31:30 amiga kernel: ohci-pci 0000:96:00.0: USB HC reset timed out!
Sep 07 08:31:30 amiga kernel: ohci-pci 0000:96:00.0: can't restart, -1
Sep 07 08:31:30 amiga kernel: ohci-pci 0000:96:00.0: HC died; cleaning up
Sep 07 08:31:30 amiga kernel: usb usb13: PM: dpm_run_callback(): usb_dev_resume+0x0/0x20 returns -1
Sep 07 08:31:30 amiga kernel: usb usb13: PM: failed to resume async: error -1
Sep 07 08:31:30 amiga kernel: ohci-pci 0000:96:00.1: USB HC reset timed out!
Sep 07 08:31:30 amiga kernel: ohci-pci 0000:96:00.1: can't restart, -1
Sep 07 08:31:30 amiga kernel: ohci-pci 0000:96:00.1: HC died; cleaning up
Sep 07 08:31:30 amiga kernel: usb usb14: PM: dpm_run_callback(): usb_dev_resume+0x0/0x20 returns -1
Sep 07 08:31:30 amiga kernel: usb usb14: PM: failed to resume async: error -1
Sep 07 08:31:30 amiga kernel: pcieport 0000:21:04.0: Unable to change power state from D3cold to D0, device inaccessible
Sep 07 08:31:30 amiga kernel: igb 0000:25:00.0 enp37s0: PCIe link lost
Sep 07 08:31:30 amiga kernel: ahci 0000:8f:00.0: AHCI controller unavailable!
Sep 07 08:31:30 amiga kernel: usb 1-3: device descriptor read/64, error -71
Sep 07 08:31:31 amiga kernel: usb 1-3: device descriptor read/64, error -71
Sep 07 08:31:31 amiga kernel: usb 1-3: device descriptor read/64, error -71
Sep 07 08:31:31 amiga kernel: usb 1-3: device descriptor read/64, error -71
Sep 07 08:31:32 amiga kernel: usb 1-3: device not accepting address 7, error -71
Sep 07 08:31:33 amiga kernel: usb 1-3: device not accepting address 8, error -71
Sep 07 08:31:33 amiga kernel: usb usb1-port3: unable to enumerate USB device
Sep 07 08:31:35 amiga kernel: xhci_hcd 0000:24:00.0: xHCI host controller not responding, assume dead
Sep 07 08:31:35 amiga kernel: xpad 11-2:1.0: xpad_try_sending_next_out_packet - usb_submit_urb failed with result -19
Sep 07 08:31:35 amiga kernel: xhci_hcd 0000:22:00.0: xHCI host controller not responding, assume dead
Sep 07 08:31:35 amiga kernel: pcieport 0000:8e:05.0: Unable to change power state from D3cold to D0, device inaccessible
Sep 07 08:31:35 amiga kernel: pcieport 0000:8e:04.0: Unable to change power state from D3cold to D0, device inaccessible
Sep 07 08:31:36 amiga kernel: ahci 0000:8f:00.0: AHCI controller unavailable!
Sep 07 08:31:42 amiga kernel: ahci 0000:8f:00.0: AHCI controller unavailable!
Sep 07 08:31:43 amiga kernel: ahci 0000:8f:00.0: AHCI controller unavailable!
Sep 07 08:31:43 amiga kernel: ahci 0000:8f:00.0: AHCI controller unavailable!
Sep 07 08:31:43 amiga kernel: md/raid0md0: Disk failure on sdd detected, failing array.
Sep 07 08:31:43 amiga kernel: ahci 0000:8f:00.0: AHCI controller unavailable!
Sep 07 08:31:43 amiga kernel: ahci 0000:8f:00.0: AHCI controller unavailable!
Sep 07 08:31:43 amiga kernel: Buffer I/O error on dev md0, logical block 0, async page read
Sep 07 08:31:43 amiga kernel: Buffer I/O error on dev md0, logical block 0, async page read
Sep 07 08:31:43 amiga kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4364b3-pcie for chip BCM4364/4
Sep 07 08:31:43 amiga kernel: brcmfmac: brcmf_c_process_txcap_blob: TxCap blob found, loading
Sep 07 08:31:43 amiga kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4364/4 wl0: Dec  9 2022 17:02:25 version 9.30.492.0.32.5.87 FWID 01-e7856862
Sep 07 08:31:44 amiga kernel: pcieport 0000:12:00.0: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Requester ID)
Sep 07 08:31:44 amiga kernel: pcieport 0000:12:00.0:   device [8086:203f] error status/mask=00004000/00000000
Sep 07 08:31:44 amiga kernel: pcieport 0000:12:00.0:    [14] CmpltTO                (First)
Sep 07 08:31:44 amiga kernel: pcieport 0000:93:05.0: Unable to change power state from D3hot to D0, device inaccessible
Sep 07 08:31:44 amiga kernel: pcieport 0000:93:04.0: Unable to change power state from D3hot to D0, device inaccessible
Sep 07 08:31:45 amiga kernel: ehci-pci 0000:96:00.2: HC died; cleaning up
Sep 07 08:31:47 amiga kernel: pcieport 0000:8a:02.0: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Requester ID)
Sep 07 08:31:47 amiga kernel: pcieport 0000:8a:02.0:   device [8086:15ea] error status/mask=00300000/00000000
Sep 07 08:31:47 amiga kernel: pcieport 0000:8a:02.0:    [20] UnsupReq               (First)
Sep 07 08:31:47 amiga kernel: pcieport 0000:8a:02.0:    [21] ACSViol               
Sep 07 08:31:47 amiga kernel: pcieport 0000:8a:02.0: AER:   TLP Header: 34000000 00000010 00000000 00000000
Sep 07 08:31:56 amiga kernel: ohci-pci 0000:96:00.1: HC died; cleaning up
Sep 07 08:31:56 amiga kernel: ohci-pci 0000:96:00.0: HC died; cleaning up
Sep 07 08:32:02 amiga kernel: usb 10-1.4: 1:1: cannot get freq at ep 0x4
Sep 07 08:32:02 amiga kernel: usb 10-1.4: 1:2: cannot get freq at ep 0x4
Sep 07 08:32:03 amiga kernel: usb 10-1.4: 2:1: cannot get freq at ep 0x84

made no difference for wake from suspend and generated more errors it seems:

dullbananas · 2024-10-12T16:10:31Z

Workaround now works in Fedora

stereo4nick mentioned this issue Jul 11, 2024

s2idle sleep mode does not work and prevent computer to completely shutdown #99

Open

6.5.7-t2 does not wake from suspend #53

6.5.7-t2 does not wake from suspend #53

Comments

aboulfad commented Oct 18, 2023

AdityaGarg8 commented Oct 18, 2023

aboulfad commented Oct 18, 2023 • edited Loading

AdityaGarg8 commented Oct 18, 2023

rydymth commented Nov 13, 2023

AdityaGarg8 commented Nov 13, 2023

rydymth commented Nov 13, 2023

AdityaGarg8 commented Nov 13, 2023

rydymth commented Nov 13, 2023

AdityaGarg8 commented Nov 13, 2023

AdityaGarg8 commented Nov 14, 2023 • edited Loading

rydymth commented Nov 14, 2023

aboulfad commented Nov 14, 2023

AdityaGarg8 commented Nov 14, 2023

aboulfad commented Nov 14, 2023

AdityaGarg8 commented Nov 14, 2023

rydymth commented Nov 14, 2023 • edited Loading

AdityaGarg8 commented Nov 14, 2023

AdityaGarg8 commented Nov 14, 2023

AdityaGarg8 commented Nov 14, 2023

aboulfad commented Nov 14, 2023

rydymth commented Nov 15, 2023 • edited Loading

AdityaGarg8 commented Nov 15, 2023 • edited Loading

rydymth commented Nov 15, 2023

AdityaGarg8 commented Nov 15, 2023

AdityaGarg8 commented Nov 15, 2023

rydymth commented Nov 15, 2023

AdityaGarg8 commented Nov 15, 2023 • edited Loading

AdityaGarg8 commented Nov 15, 2023

AdityaGarg8 commented Nov 15, 2023

rydymth commented Nov 15, 2023

AdityaGarg8 commented Jan 2, 2024

mdsheraj123 commented Jan 7, 2024 • edited Loading

nicovell3 commented Jan 12, 2024

AdityaGarg8 commented Jan 12, 2024

aboulfad commented Jan 12, 2024 • edited Loading

nicovell3 commented Jan 12, 2024

Simon-Martens commented Feb 1, 2024 • edited Loading

AdityaGarg8 commented Feb 2, 2024

aboulfad commented Feb 2, 2024

Simon-Martens commented Feb 2, 2024 • edited Loading

AdityaGarg8 commented Feb 2, 2024

aboulfad commented Feb 2, 2024

riddlework commented Apr 1, 2024

AdityaGarg8 commented Apr 2, 2024

POMATu commented Apr 29, 2024 • edited Loading

AdityaGarg8 commented Apr 29, 2024

POMATu commented Apr 29, 2024 • edited Loading

AdityaGarg8 commented Apr 29, 2024 • edited Loading

POMATu commented Apr 30, 2024 • edited Loading

POMATu commented May 2, 2024 • edited Loading

rydymth commented Jun 9, 2024

stereo4nick commented Jun 15, 2024 • edited Loading

AdityaGarg8 commented Jun 16, 2024

angelobdev commented Jun 16, 2024 • edited Loading

POMATu commented Jul 9, 2024

stereo4nick commented Jul 10, 2024 • edited Loading

AdityaGarg8 commented Jul 11, 2024

CaptainMorgan12 commented Sep 7, 2024 • edited Loading

dullbananas commented Oct 12, 2024

aboulfad commented Oct 18, 2023 •

edited

Loading

AdityaGarg8 commented Nov 14, 2023 •

edited

Loading

rydymth commented Nov 14, 2023 •

edited

Loading

rydymth commented Nov 15, 2023 •

edited

Loading

AdityaGarg8 commented Nov 15, 2023 •

edited

Loading

AdityaGarg8 commented Nov 15, 2023 •

edited

Loading

mdsheraj123 commented Jan 7, 2024 •

edited

Loading

aboulfad commented Jan 12, 2024 •

edited

Loading

Simon-Martens commented Feb 1, 2024 •

edited

Loading

Simon-Martens commented Feb 2, 2024 •

edited

Loading

POMATu commented Apr 29, 2024 •

edited

Loading

POMATu commented Apr 29, 2024 •

edited

Loading

AdityaGarg8 commented Apr 29, 2024 •

edited

Loading

POMATu commented Apr 30, 2024 •

edited

Loading

POMATu commented May 2, 2024 •

edited

Loading

stereo4nick commented Jun 15, 2024 •

edited

Loading

angelobdev commented Jun 16, 2024 •

edited

Loading

stereo4nick commented Jul 10, 2024 •

edited

Loading

CaptainMorgan12 commented Sep 7, 2024 •

edited

Loading