I found it:
Yes, it is! I have this issue one time per day or two even despite relatively recent mesa version (22.3.6).
The new kernel is unfortunately not yet available.
My Librem 5 has a new issue today, susped is disabled (and I removed swap partition) but there are some kind of crash during active use when screen and buttons become unresponsive. But it is not in a completely frozen state, at some moments screen moves, responding gestures I had minutes ago and freezes again. It is now in this frozen state… No, just when writing this phrase I take back control of it ! Let’s see the logs.
There are a very huge amount of logs and it’s difficult for me to select the most accurate parts
This strange behavior started when I opened several apps at the same time, it may be RAM saturation or CPU overload 
.
May this issue be related to the defficient kernel ?
2 Likes
It is now.
2 Likes
Great. Thanks to all who worked on this!
1 Like
Thank you so much ! I upgraded and I’ll keep you informed
2 Likes
For now I didn’t exerienced resume from suspend issue ! But I had RAM saturation issues until I followed your instructions. Looks promising for now but needs further testing. I noticed that it’s not persistant after reboot
1 Like
I found two solutions to make it persistent: Look at my post again
1 Like
Let’s continue the topic of “crashes”. I’ve updated the kernel to 6.6.34 and was not able to resume my L5 today morning. The device was working (ssh works) but the screen remained blank. The log was flooded by a message:
1 Like
If you still have ssh access, can’t you revert the kernel change?
1 Like
In my side I still haven’t resume from suspend issue. If you have SSH access it should be something else, maybe a phosh crash ? You can log in through SSH and type ‘sudo systemctl restart phosh.service’. I had phosh crashes on my pinephones running Mobian but until now never on my L5.
PS: I’m sad because I dropped my L5 on rock last night. It fell on the lower right corner that is damaged, screen is fortunately intact
2 Likes
Still no frrozen state for me anymore. I did other tests with extended zram. 5GB seems to be the optimum (size-fraction = 2). I tried untill 13.3GB (and untill size-fraction = 6) without problem too. I had no crash for hours except untill I opened all my apps one after another and got over 9GB of total memory usage+heavy cpu load. At lower usage I get full stability now. Is is a dream. (see my own post for the procedure)
3 Likes
At this moment I observed the same issue a few times… May be one time per day. Auto-suspend is on, wifi is off during suspend. No crashes during a charger or nexdock plug. L5 really does get better!
2 Likes
I hasn’t resume from suspend issue for one and half week until now. It has just happening
2 Likes
Could you provide the log just before reboot?
I have 4 days uptime at this moment. Only one thing bother me - suspend does not work if the phone was resumed in my pocket by, e.g., SMS due to high screen sensitivity. So, I’m thinking about the script which will force suspend in case if you do not enter a pin code…
1 Like
The battery isn’t fully drained yet.
Habitually due to poor battery life I turn it off in the evening before going to sleep.
Yes this script would be a great idea, I happened to me too to not suspend when in pocket
1 Like
Hello, I waited until this morning and couldn’t restart the L5 by plugging in I even couldn’t force reset ! So I retired the battery, it was 2%…
I read the logs but it’s strange, I see no error message
juil. 20 13:37:07 pureos systemd-sleep[6595]: Suspending system...
juil. 20 13:37:07 pureos systemd[1]: Starting Suspend...
juil. 20 13:37:07 pureos kernel: edt_ft5x06 2-0038: Unable to fetch data, error: -6
juil. 20 13:37:07 pureos systemd[1]: Reached target Sleep.
juil. 20 13:37:07 pureos NetworkManager[721]: <info> [1721475427.6242] device (cdc-wdm0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
juil. 20 13:37:07 pureos mmsdtng[901]: ../src/service.c:mms_service_set_bearer_handler() service 0xaaaad1a62ba0 handler 0xaaaab88b5a20
juil. 20 13:37:07 pureos mmsdtng[901]: ../plugins/modemmanager.c:mmsd_mm_state() Setting Bearer Handler
juil. 20 13:37:07 pureos mmsdtng[901]: ../plugins/modemmanager.c:mmsd_mm_state() MMSD_MM_STATE_READY
juil. 20 13:37:07 pureos mmsdtng[901]: ../plugins/modemmanager.c:mmsd_mm_get_modem_state() MM_MODEM_GOOD_STATE: 8
juil. 20 13:37:07 pureos mmsdtng[901]: ../plugins/modemmanager.c:modem_state_changed_cb() State Change: Old State: 9 New State: 8, Reason: 1
juil. 20 13:37:07 pureos NetworkManager[721]: <info> [1721475427.6075] device (cdc-wdm0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
juil. 20 13:37:07 pureos NetworkManager[721]: <info> [1721475427.6062] modem["cdc-wdm0"]: modem state changed, 'disconnecting' --> 'registered' (reason: user-requested)
juil. 20 13:37:07 pureos ModemManager[833]: <info> [modem0/bearer1] connection #11 finished: duration 1110s, tx: 278222 bytes, rx: 2621627 bytes
juil. 20 13:37:07 pureos ModemManager[833]: <info> [modem0] state changed (disconnecting -> registered)
juil. 20 13:37:07 pureos mmsdtng[901]: ../src/service.c:mms_service_set_bearer_handler() service 0xaaaad1a62ba0 handler 0xaaaab88b5a20
juil. 20 13:37:07 pureos mmsdtng[901]: ../plugins/modemmanager.c:mmsd_mm_state() Setting Bearer Handler
juil. 20 13:37:07 pureos mmsdtng[901]: ../plugins/modemmanager.c:mmsd_mm_state() MMSD_MM_STATE_READY
juil. 20 13:37:07 pureos mmsdtng[901]: ../plugins/modemmanager.c:mmsd_mm_get_modem_state() MM_MODEM_GOOD_STATE: 9
juil. 20 13:37:07 pureos mmsdtng[901]: ../plugins/modemmanager.c:modem_state_changed_cb() State Change: Old State: 11 New State: 9, Reason: 1
juil. 20 13:37:07 pureos NetworkManager[721]: <info> [1721475427.5822] modem["cdc-wdm0"]: modem state changed, 'connected' --> 'disconnecting' (reason: user-requested)
juil. 20 13:37:07 pureos ModemManager[833]: <info> [modem0] state changed (connected -> disconnecting)
juil. 20 13:37:07 pureos systemd-networkd[529]: wwan0: Lost carrier
juil. 20 13:37:07 pureos systemd-networkd[529]: wwan0: Link DOWN
juil. 20 13:37:07 pureos systemd[1]: Started Network Manager Script Dispatcher Service.
juil. 20 13:37:07 pureos dbus-daemon[720]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
juil. 20 13:37:07 pureos systemd[1]: Starting Network Manager Script Dispatcher Service...
juil. 20 13:37:07 pureos dbus-daemon[720]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.9' (uid=0 pid=7>
juil. 20 13:37:07 pureos NetworkManager[721]: <info> [1721475427.3976] device (cdc-wdm0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
juil. 20 13:37:07 pureos NetworkManager[721]: <info> [1721475427.3942] manager: NetworkManager state is now ASLEEP
juil. 20 13:37:07 pureos systemd-networkd[529]: usb0: Link DOWN
juil. 20 13:37:07 pureos NetworkManager[721]: <info> [1721475427.3750] device (usb0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
juil. 20 13:37:07 pureos ModemManager[833]: <info> [sleep-monitor] system is about to suspend
juil. 20 13:37:07 pureos NetworkManager[721]: <info> [1721475427.3746] manager: sleep: sleep requested (sleeping: no enabled: yes)
juil. 20 13:37:03 pureos kernel: bq25890-charger 3-006a: Disabling OTG_EN pin
juil. 20 13:37:03 pureos kernel: bq25890-charger 3-006a: Upstream supply changed: 1.
juil. 20 13:37:03 pureos kernel: bq25890-charger 3-006a: Disabling OTG_EN pin
juil. 20 13:37:03 pureos kernel: bq25890-charger 3-006a: Upstream supply changed: 1.
juil. 20 13:37:03 pureos kernel: bq25890-charger 3-006a: Disabling OTG_EN pin
juil. 20 13:37:03 pureos kernel: bq25890-charger 3-006a: Upstream supply changed: 1.
juil. 20 13:37:03 pureos kernel: bq25890-charger 3-006a: NTC state UNKNOWN
juil. 20 13:37:03 pureos kernel: bq25890-charger 3-006a: Disabling OTG_EN pin
juil. 20 13:37:03 pureos kernel: bq25890-charger 3-006a: Upstream supply changed: 1.
juil. 20 13:37:02 pureos kernel: bq25890-charger 3-006a: NTC state normal
As I previously said I’m afraid to physically damage it if this reproduces…
1 Like
Hi. I do not want to hijack your thread, but I am also experiencing frequent crashes directly associated with suspend and USB power issues.
I am experiencing this only since the last kernel upgrade.
Interestingly, I cannot access the settings menu at all when on battery power. However, when I plug in anything to the USB C slot, I can access settings. Very odd. This points to a clear power issue associated with the USB and suspend.
Finally, the device crashes spontaneously when heated enough to create a state of no-charge (flashing red light). Suspend is totally broken for me now. All it does is turn off my device.
I wonder, should I simply reflash the device?
2 Likes
Another thought I had was to maybe downgrade to the previous kernel?
1 Like