L14 freezing on battery with Pureboot 30

Firmware PureBoot/Heads
, ,
1

I had been using my Librem 14 for more than two years without any issues. Usually, every now and then I update the firmware to the latest version.

Unfortunately, right after updating to Pureboot 30 the computer started to freeze, sometimes very soon after booting, sometimes after a few minutes more. First no keyboard input is recognized, a little later the mouse stops moving.
Eventually I noticed, that it only seems to happen when the charger is not plugged in.

I tried downgrading to Pureboot 29 and the freezes seem to be gone.

Is there anything I can do about it? I don’t want to be stuck on version 29 forever.

1 Like
2

@jonathon.hall since you’re the author of the commits in the firmware/releases repository it would be nice if you read my post.

1 Like
3

@frog Sorry that I didn’t see this. I haven’t been able to read every forum thread due to many needs competing for my time, but I have been trying to keep up with mentions - so I’m glad you mentioned me here.

Thanks for confirming that this is a regression in PureBoot 30. I haven’t noticed it on mine, but let me run some more tests with the system on battery only, that’s an important detail (thanks for finding that!).

If I can reproduce it, I can bisect it myself. (PureBoot itself has little do to with hardware in any way that could cause freezes, this is most likely an upstream change from coreboot.) If not, I can work with you to bisect, but let me do as much as I can on my side first.

I don’t want you to be stuck on PB 29 forever either!

3 Likes
4

Same for me like frog.
flashed, boot, then freezes after some minutes, sometimes one hour.

1 Like
5

I have seen similar symptoms with my Librem 14 after upgrading to PureBoot 30, though I also upgraded the kernel around the same time so that can’t be ruled out yet either.

The lines that consistently show up in my system journal right before the freezes are:

kernel: i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out
kernel: i915 0000:00:02.0: [drm] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}

Often I also see a GPU hang error, but not always.
Do others see similar messages after these freezes?

I can somewhat confirm it happens more frequently on battery though I have gotten one or two while charging over USB-C.

1 Like
6

Sorry to reopen the thread,

I was running the coreboot version for some months or a year now. I have always EC and OS updated (PureOS)

Some weeks ago, suddenly resuming from hibernation was not working, but not always. I ended with installing the version 30 and have the same problem again with freezing.

Here some logs before the freeze:

août 30 22:01:34 lionel-librem14-pureos opensnitch_ui.desktop[2694]: ERROR:dbus.connection:Exception in handler for D-Bus signal:

août 30 22:01:34 lionel-librem14-pureos opensnitch_ui.desktop[2694]: Traceback (most recent call last):

août 30 22:01:34 lionel-librem14-pureos opensnitch_ui.desktop[2694]: File “/usr/lib/python3/dist-packages/dbus/connection.py”, line 232, in maybe_handle_message

août 30 22:01:34 lionel-librem14-pureos opensnitch_ui.desktop[2694]: self._handler(*args, **kwargs)

août 30 22:01:34 lionel-librem14-pureos opensnitch_ui.desktop[2694]: File “/usr/lib/python3/dist-packages/notify2.py”, line 154, in _closed_callback

août 30 22:01:34 lionel-librem14-pureos opensnitch_ui.desktop[2694]: n = notifications_registry[nid]

août 30 22:01:34 lionel-librem14-pureos opensnitch_ui.desktop[2694]: KeyError: 110

août 30 22:01:34 lionel-librem14-pureos opensnitch_ui.desktop[2694]: ERROR:dbus.connection:Exception in handler for D-Bus signal:

août 30 22:01:34 lionel-librem14-pureos opensnitch_ui.desktop[2694]: Traceback (most recent call last):

août 30 22:01:34 lionel-librem14-pureos opensnitch_ui.desktop[2694]: File “/usr/lib/python3/dist-packages/dbus/connection.py”, line 232, in maybe_handle_message

août 30 22:01:34 lionel-librem14-pureos opensnitch_ui.desktop[2694]: self._handler(*args, **kwargs)

août 30 22:01:34 lionel-librem14-pureos opensnitch_ui.desktop[2694]: File “/usr/lib/python3/dist-packages/notify2.py”, line 154, in _closed_callback

août 30 22:01:34 lionel-librem14-pureos opensnitch_ui.desktop[2694]: n = notifications_registry[nid]

août 30 22:01:34 lionel-librem14-pureos opensnitch_ui.desktop[2694]: KeyError: 110

août 30 22:06:34 lionel-librem14-pureos brltty[994]: brltty: USB control transfer error 110: Connexion terminée par expiration du délai d’attente

août 30 22:06:34 lionel-librem14-pureos kernel: usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd brltty rqt 128 rq 6 len 255 ret -110

août 30 22:06:35 lionel-librem14-pureos brltty[994]: USB control transfer error 110: Connexion terminée par expiration du délai d’attente

août 30 22:06:35 lionel-librem14-pureos brltty[994]: brltty: USB control transfer error 110: Connexion terminée par expiration du délai d’attente

août 30 22:06:35 lionel-librem14-pureos kernel: usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd brltty rqt 128 rq 6 len 255 ret -110

août 30 22:06:36 lionel-librem14-pureos brltty[994]: USB control transfer error 110: Connexion terminée par expiration du délai d’attente

août 30 22:06:36 lionel-librem14-pureos brltty[994]: brltty: USB control transfer error 110: Connexion terminée par expiration du délai d’attente

août 30 22:06:36 lionel-librem14-pureos kernel: usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd brltty rqt 128 rq 6 len 255 ret -110

……

août 30 22:01:58 lionel-librem14-pureos gnome-shell[2445]: libinput error: event12 - HTIX5288:00 0911:5288 Touchpad: client bug: event processing lagging behind by 23ms, your system is too slow

août 30 22:01:58 lionel-librem14-pureos gnome-shell[2445]: libinput error: event12 - HTIX5288:00 0911:5288 Touchpad: WARNING: log rate limit exceeded (5 msgs per 60min). Discarding future messages

1 Like
7

Try first:

 sudo apt purge brltty*

Try second: getting more logs..

 dmesg | grep -iE 'error|fail|bug|panic|warn'
1 Like
8

Thank you. Here it is:

[17742.048782] printk: Suspending console(s) (use no_console_suspend to debug)
[17743.560115] usb 2-6: Disable of device-initiated U1 failed.
[17743.567122] usb 2-6: Disable of device-initiated U2 failed.
[17744.123823] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] ERROR mstb 00000000a76e726b port 5: DPCD read on addr 0x4b0 for 1 bytes NAKed
[17744.188128] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] ERROR mstb 00000000a76e726b port 6: DPCD read on addr 0x4b0 for 1 bytes NAKed
[17744.294782] r8169 0000:02:00.0: firmware: failed to load rtl_nic/rtl8168h-2.fw (-2)
[17744.294788] r8169 0000:02:00.0: Direct firmware load for rtl_nic/rtl8168h-2.fw failed with error -2
[17745.137199] r8152 2-3.1:1.0: firmware: failed to load rtl_nic/rtl8153b-2.fw (-2)
[17745.137203] r8152 2-3.1:1.0: Direct firmware load for rtl_nic/rtl8153b-2.fw failed with error -2
[17750.405060] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] ERROR mstb 00000000a76e726b port 5: DPCD read on addr 0x4b0 for 1 bytes NAKed
[17750.463910] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] ERROR mstb 00000000a76e726b port 6: DPCD read on addr 0x4b0 for 1 bytes NAKed

1 Like
9

Downgrade to Pureboot 29, if persist go to 28.

Please share a Hi-Res photo of the computer bottom, aside with the charger where the charging specifications are shown. Looks like a issue on power-saving states.

1 Like
10

Since my last post, I am with the 30 and it is working like a charm again (Hibernation and no freeze). So I guess removing britty was the right solution! I will tell if I get the problem again.

2 Likes
11

Actually, i’ve had a new freeze and looked into the logs, then uninstall surfshark. Since then, it seems ok.

2 Likes