My laptop keeps on freezing randomly

[rene]

First just don’t do anything; I may be barking up a completely wrong tree here

It’s otherwise not related to Manjaro; you’d enter your BIOS-setup by tapping e.g. the Del key, or F2 or F9, or … when the system starts up and then look around for anything suspicious. But for now just wait and see.

[chicho1704]

ohh ok, ok
Thank You!!
I`ll just wait and see

[chicho1704]

@rene

I may be barking up a completely wrong tree here

[bogdancovaciu]

@chicho1704

5.19.17-1-MANJARO

Please switch to a supported kernel or LTS one, as the one you are using is EOL.

@chicho1704

  Sound Server-2: PulseAudio v: 16.1 running: yes
  Sound Server-3: PipeWire v: 0.3.59 running: yes

Might want to address that too, was covered multiple times on the forum.

@chicho1704

Swap:
  Alert: No swap data was found.

Use at least a swapfile, or use zram-generator package from repositories.

Edit: Also, just saw that

@chicho1704

could not read from '/sys/module/pcc_cpufreq/initstate': No such device

Kernel 5.8.x my system seems to be only running at it’s minimum clock of 800mhz

try one value at time you can pres Esc on Grub (e) dit and add one value option for test then F10 try this value intel_pstate=active

[chicho1704]

@bogdancovaciu

Please switch to a supported kernel or LTS one, as the one you are using is EOL.

@chicho1704

LTS freezing was worse than with the one I am using right now.

@bogdancovaciu

Might want to address that too, was covered multiple times on the forum.

What do you mean by this?

@Kernel 5.8.x my system seems to be only running at it’s minimum clock of 800mhz

try one value at time you can pres Esc on Grub (e) dit and add one value option for test then F10 try this value intel_pstate=active

how can I do it?

Thank You Very Much

[bogdancovaciu]

@chicho1704

LTS freezing was worse

Because maybe you have to take care of the other things i mentioned too.

@chicho1704

What do you mean by this?

When both audio servers run, in some instances, on some systems things can start to choke. Happened on one of my installs. Here is how to avoid that, if that could be part of your issue.

Steinberg soundcard stopped working

Hello, By this i gather you should either properly switch to pipewire or properly keep using pulseaudio, but not both at the same time. With pipewire there are some advantages tho. By installing manjaro-pipewire and pipewire-media-session instead of wireplumber all should be fine.

@chicho1704

how can I do it?

Same as explained from here:

@rene

You’d want to try to boot with the kernel parameter

but you use the intel_pstate=active kernel parameter instead.

[chicho1704]

@bogdancovaciu

but you use the intel_pstate=active kernel parameter instead

How can i boot with the kernel parameter?

[chicho1704]

@bogdancovaciu

When both audio servers run, in some instances, on some systems things can start to choke. Happened on one of my installs. Here is how to avoid that, if that could be part of your issue.

Ok I get it… How can I uninstall pulseaudio?

[bogdancovaciu]

There are two ways:

• on Grub boot menu you press the e key and then on the Linux Kernel Line, you add right after the quiet the intel_pstate=active and then press F10 to save it and continue booting. That is not a permanent entry
• or permanent entry, by editing the file

@rene

sudo nano /etc/default/grub

but honestly, there is no point to repeat that …

@chicho1704

pulseaudio

You don’t. is required, but in order to not keep it active you simply install manjaro-pipewire and will do for you all is required. Just reboot after that to take effect.

[chicho1704]

@bogdancovaciu

There are two ways:

• on Grub boot menu you press the e key and then on the Linux Kernel Line, you add right after the quiet the intel_pstate=active and then press F10 to save it and continue booting. That is not a permanent entry
• or permanent entry, by editing the file

ohh This I did already before your first post

[bogdancovaciu]

@chicho1704

This I did already before your first post

You probably did it with the EOL kernel …

[chicho1704]

oh yes
now I am using the LTS kernel… do I need to redo it?

[bogdancovaciu]

@chicho1704

do I need to redo it?

If you did it from GRUB menu, then yes, you lose that upon reboot.
If you did it on /etc/default/grub then updated grub, then you don’t have to do it again.

[chicho1704]

ok so I don’t have to do it again… I checked and it’s still there

[chicho1704]

Thank You Very Much!!
I have done all so far except swap…
To do so I just need to install zram-generator package from repositories?

[rene]

You can, but if you now also add the by bogdancovaciu advised “intel_pstate=active” kernel parameter then you won’t know if it was that one or the earlier advised “intel_idle.max_cstate=0” parameter which you added before. It’s in that sense probably useful to test either in isolation – at the moment

cat /proc/cmdline

should be saying that you are running with “intel_idle.max_cstate=0”. If you let it run long enough to be satisfied that it’s now not freezing you’d have pinpointed it to that intel_idle driver.

I.e., again my advise is to for now sit back and do nothing until either the system freezes again or you’re satisfied that it won’t anymore.

[chicho1704]

is this correct, then?

[euki@euki ~]$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.15-x86_64 root=UUID=846d6e8e-7a8e-4beb-94b0-3f6d858347d2 rw quiet apparmor=1 security=apparmor udev.log_priority=3 intel_idle.max_cstate=0

[rene]

Yup. If the system’s now stable for long enough without rebooting it’ll be confirmed that it’s that c-state thing again. You can in that case keep things as they are, try “intel_idle.max_cstate=1” instead, or as mentioned try and rummage through your BIOS setup (I believe it’s by the way for your machine a matter of tapping F10 while it’s starting to get there) to see if there’s anything possibly related to set there.

But, then, for now please just do nothing

[chicho1704]

ok… i did chage the audio settings and installed manjaro-pipewire
as a matter of fact the system is stable now

[rene]

Okay, if you’re satisfied that the system’s stable now, it’s supposedly fixed by the “intel_idle.max_cstate=0” kernel parameter. bogdancovaciu’s advised “intel_pstate=active” is a little too related though for me to feel confident that it wouldn’t also fix things for you and if that one gets rid of that

could not read from '/sys/module/pcc_cpufreq/initstate': No such device`

error message, seems you want it anyway, so it would in that case be better.

That is, what I would do is:

1. Change /etc/default/grub again to instead of “intel_idle.max_cstate=0” have “intel_pstate=active” in that GRUB_CMDLINE_LINUX_DEFAULT=“…” string as before, save the file, rerun “sudo update-grub”, reboot and see if things are stable now also.

If yes, and certainly if indeed also that above “no such device” error is gone, go to 3. If not:

2. Change /etc/default/grub again to additionally have besides “intel_pstate=active” also “intel_idle.max_cstate=0” in GRUB_CMDLINE_LINUX_DEFAULT=“…” , save the file, rerun “sudo update-grub”, reboot and see if things are stable now.

Supposedly they are and supposedly/hopefully still that “no such device” error is gone. If not, remove the “intel_pstate=active” again (and save, rerun sudo update-grub, etc…) but that would be unexpected. So if stable as expected, try for possibly better battery life:

3. Change /etc/default/grub again to now have “intel_idle.max_cstate=1” instead (still alongside the pstate one), save, etc, etc, and see again.

If still stable, keep it at that – or tap F10 during boot to enter your machine’s BIOS setup and try and see if there’s a settable option there that looks related and that also fixes things without you needing that intel_idle.max_cstate option at all. Sort of doubt it on a laptop, but you can supposedly just see – you’d of course need to remove the option from /etc/default/grub (and save, rerun, etc, etc) to test the effects of any possibly found BIOS option in isolation.