SMG wrote: ⤴Fri Dec 10, 2021 10:02 am
That appears to be the case. I checked my results and they are 9 so your computer is at the other end of the scale.
Thanks for still being here
Yes I agree - we must be missing something .....
I disabled c-states on all three computers last night. My partner uses the generic kernel laptop for her daily work. Nothing fancy, generic kernel, Crossover Office with MS Office, Libreoffice, Waterfox browser, Evolution e-mail, Nemo, a bit of audio playback of files. Despite c-states being off, she experienced lock-ups today as usual. There is no special audio setting on her laptop, no low-latency setting etc of any kind. Timeshift is on. A couple of nfs4 shares to a NAS in fstab, but that shouldn't really be a problem because I've had countless Linux installations connect to a NAS via nfs4 for almost a decade.
The desktop computer I use is the only one of the three computers that was running Mint before v20. 19.3 was smooth and had the same Ubuntu Studio low latency tweaks activated. No real issues. What I don't remember is if 19.3 was installed on btrfs or ext4, also unsure if Timeshift was on (I think so). Any kind of power supply issue would have had to be there with 19.3 too, right? I don't remember having lock-up issues with Mint 20 or 20.1 - there were other issues but no lock-ups. I first became aware of the lock-up around end of June I think, possibly because I was trying out daily builds via the ppa. My partner started experiencing lock-ups from July/August. Could this have been caused by upgrading from 20.1 to 20.2? Or could it have been a kernel switch, from 5.4 to 5.10/11?
The only thing that all three computers have in common is that they all run off NVMes with btrfs and Timeshift activated.
Both laptops are encrypted and installed as per this guide
https://mutschler.eu/linux/install-guid ... rfs-20-04/
Both laptops have swap files, the desktop has a swap partition.
Whilst I do time-critical work (ie record music), a lot of my usage is non time-critical: browsing, editing audio files, the usual office and graphics stuff. I still get those lock-ups with non time-critical work - but 10-45 sec enforced breaks shouldn't really happen, at least not on reasonable well-equipped computers, in particular if those computer(s) was/were running fine with a previous version.
I could try 5.4 again and see what happens.
Appreciate it that you haven't written me off as a lost cause yet