Closed
Description
When booting from the image and running the rootfs on an USB-C port, regardless if you're behind a (powered) hub or not: When the system goes into suspend, the root filesystem becomes unoperable (readonly).
Probable cause: Some lack in the power management. There are some messages in dmesg that say not everything is working:
[ 2.049181] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with usb0-sbu-mux
[ 2.056263] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with usb1-sbu-mux
[ 2.230842] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with a600000.usb
[ 2.248853] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with ae90000.displayport-controller
[ 2.251678] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with ae98000.displayport-controller
[ 2.944111] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with a800000.usb
usb0-sbu-mux and usb1-sbu-mux are USB-C, like a600000.usb and a800000.usb are. Funnily enough, USB2 (a400000.usb) which is 3x USB-A and the internal RTL8152 GbE-Port doesn't have this issue, and it works with suspend as expected.