Is anyone else experiencing freezing issues with Librem 15 v3?


#61

I’m having the same issue. I’m running a librem 15v3 with reflashed coreboot and Qubes OS 4.0.
The freezes occur sometimes during boot-up when Grub asks me for a passphrase (and right then the system freezes, so I can’t type any keys) and sometimes when I’m running the OS and doing my normal work the system just suddenly freezes.
I would like to give you more info, but currently my system is hung up in the issue described at Librem 15 won’t turn on.
I’m using coreboot version 4.7-Purism-4 as well. This suggests that it might not be a debian (or PureOS) specific issue.
I also still get this issue also after specifying intel_pstate=disable to the kernel args via the grub menu.


#62

Adding the kernel arg i915.enable_rc6=0, removed the issues with grub, however now my system starts freezing during normal use even more (it appears) and less randomly so (starting a browser usually freezes the system).


#63

I’m still seeing intermittent freezes on 13v2 with 4.7-Purism-4.


#64

Actually, the kernel arg fixes the issue with grub only most of the time (90% or more). It tried various other combination of kernel args (including intel_pstate=disable), it doesn’t help either.


Trying IOMMU with KVM causes hard freeze
#65

grub loads before (and independently of) the kernel, so kernel args shouldn’t have any impact on it… Unless it’s something about the state in which the GPU was when linux turned it off the previous time maybe, but that’s getting complicated…

I actually still have some glitches as well from time to time that make me reboot to clear it up, but I’m talking like once every few weeks of intense usage so I’ll probably just live with it…


#66

Eh, it looks like I shouldn’t have written that, I’ve gotten 4 hard crashes in these past few days, with and without intel_pstate=disable -_-
(always while a video or game was running so involving GPU activity, and mostly when I was also compiling something in the background but not always; pretty much the same as the original posts for a while back; none of the time did the network hold up to ssh in and I couldn’t get kdump to work either possibly because of encryption, I’ll try to point it to a plain device next)

I guess a kernel upgrade made it worse somehow, but honestly at this point I’m putting it on a bad series where the hardware tolerance would have gotten pushed too close to the limits and was going to let it slide, but if it’s happening more often again I guess I’ll have to spend some more time on this…


#67

@ everyone - my 2 cents …
it’s not a PureOS issue. it’s not a debian issue. it’s not even Fedora or CentOS related it is about the free drivers (linux kernel or video drivers not firmware)
i’ve been running all these distributions on the same desktop hardware for many months and the same freezing happens at random intervals requires imediate reboot. this happened with both X-org and Wayland on each distribution no proprietary software drivers installed. just the one that shipped with each distribution. all 2018.
with windows and proprietary drivers this never happened. it is not a question of firmware here. just drivers.
the hardware in use was
amd ryzen 1800x on asrock itx x370 with quadro k1200 eGPU samsung 960 evo
then the same happened on
amd ryzen 2200g on asrock itx x370 with vega 8 iGPU samsung 960 evo
it is not a matter of PureOS only it is everywhere there is Linux and open source drivers. they are not optimized.
windows is optimised so it doesn’t freeze so it doesn’t need to restart so it can spy more. yay !


#68

I have an interesting updated for all concerned on this post… I have had no screen freezing issues for several months now!!!

What has changed? My laptop crashed from running out of battery power, an issue that I still haven’t managed to fix. However, an incomplete update/upgrade meant the machine was not rebooting. I was not able to fix the broken installs, my linux knowledge is too shallow and I just don’t have the time to dive into this, so I decided to simply re-install. However, a fresh installation on an encrypted partition does not work and I therefore had to do a default install on an non-encrypted partition, along with a swap partition (which my previous factory-install did not have).

Since then I haven’t had a single issue with screen freeze. So could it be a due to a lack of swap partition or encrypted partition or maybe both that is at the root of this issue?


#69

that is a solid no. i’ve tested it like you describe on much more hardware and software combination and it is not the issue.

in the future i will try with a debian stable with xorg non proprietary drivers on my hardware to see if the issue remains the same and i will update here at such point.


#70

Yeah, I don’t think it’s directly any of that. The more time passes and the more convinced I am it has something to do with power circuits failing somewhere, at least in my case.

  • carefully keeping a power setting for the cpu is usually safe for me (e.g. powersave or performance)
  • yesterday I’ve had a couple of crashes with powersave while playing videos as usual, which hadn’t been happening so much lately, and I just noticed the power chord was unplugged so the difference from usual is that I was on battery only. I’m not sure if that is because the power supply was different or if the energy consumption plan changed due to being on battery.
  • crash never happens when computer is idle and simple continuous CPU or memory stress tests do not bring it down, but usually loads that make the power consumption vary a lot will crash it: video playback that uses half of a core if normal throttling applies keep varying the frequency and thus power consumption; and video decoding uses sse/vector instructions which are more energy intensive than normal workload.
    I also got crashes compiling big projects, that is a lot of cpu ups and downs + burst writes to disk.

I don’t see what swap would have to do with that, but disk encryption makes your CPU use AES instructions which also consume slightly more power when you read/write to disk, so that could make a slight difference there as well.

Speaking of disks I did try removing the sata drive but I don’t think I ever tried running without the nvme disk; I guess it’s worth a try.

Anyway, I’ve pretty much given up on this one. My laptop usage is simple enough that I won’t crash often if I’m a bit careful so I’ll bear with it for the life span of the laptop; after half a year of seriously using the librem15 I’m much more annoyed at the touchpad quirks/keyboard layout than this random crash issue :stuck_out_tongue: